🐛 [firebase_crashlytics] Failed to retrieve settings from https://firebase-settings.crashlytics.com

Bug report
I added firebase_crashlytics to a new flutter app and ran it. In logs, it simply logs this error and my crashes are not reported to firebase console:
E/FirebaseCrashlytics(23176): Failed to retrieve settings from https://firebase-settings.crashlytics.com/spi/v2/platforms/android/gmp/1:639321596024:android:2e8626b6d04d73c1aecd8d/settings

I hit this URL manually and it returns a 403 error. Not sure if it is expected or not.
Steps to reproduce
Steps to reproduce the behavior:

Create a new flutter app.
Create a new firebase app.
Add firebase_crashlytics plugin to flutter.
Configure the android build.gradle files.
Run the app.

Expected behavior
The crashes should be logged in firebase upon next launch of app.

Additional context
I followed the tutorial here to add crashlytics: https://firebase.flutter.dev/docs/overview/

Flutter doctor
Click To Expand
[✓] Flutter (Channel stable, 1.20.4, on Mac OS X 10.15.7 19H2, locale en-GB)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 12.0.1)
[✓] Android Studio (version 4.0)
[✓] VS Code (version 1.49.2)
[✓] Connected device (1 available)

• No issues found!

Flutter dependencies
Click To Expand
Dart SDK 2.9.2
Flutter SDK 1.20.4
rideTracker 1.0.0+1

dependencies:
- cupertino_icons 0.1.3
- device_info 0.4.2+8 [flutter device_info_platform_interface]
- firebase_core 0.5.0 [firebase_core_platform_interface flutter quiver meta firebase_core_web]
- firebase_crashlytics 0.2.0 [flutter stack_trace firebase_core firebase_core_platform_interface firebase_crashlytics_platform_interface]
- flutter 0.0.0 [characters collection meta typed_data vector_math sky_engine]
- flutter_localizations 0.0.0 [flutter intl characters collection meta path typed_data vector_math]
- provider 4.3.2+2 [flutter nested collection]
- sailor 0.7.1 [flutter]

dev dependencies:
- flutter_launcher_icons 0.8.0 [image args yaml]
- flutter_native_splash 0.1.9 [yaml image color]

transitive dependencies:
- archive 2.0.13 [crypto args path]
- args 1.6.0
- characters 1.0.0
- charcode 1.1.3
- collection 1.14.13
- color 2.1.1
- convert 2.1.1 [charcode typed_data]
- crypto 2.1.5 [collection convert typed_data]
- device_info_platform_interface 1.0.1 [flutter meta plugin_platform_interface]
- firebase 7.3.0 [http http_parser js]
- firebase_core_platform_interface 2.0.0 [flutter meta plugin_platform_interface quiver]
- firebase_core_web 0.2.0 [firebase firebase_core_platform_interface flutter flutter_web_plugins meta js]
- firebase_crashlytics_platform_interface 1.0.0 [flutter meta collection firebase_core plugin_platform_interface]
- flutter_web_plugins 0.0.0 [flutter characters collection meta typed_data vector_math]
- http 0.12.2 [http_parser path pedantic]
- http_parser 3.1.4 [charcode collection source_span string_scanner typed_data]
- image 2.1.18 [archive xml meta]
- intl 0.16.1 [path]
- js 0.6.2
- matcher 0.12.8 [stack_trace]
- meta 1.1.8
- nested 0.0.4 [flutter]
- path 1.7.0
- pedantic 1.9.0
- petitparser 3.0.4 [meta]
- plugin_platform_interface 1.0.2 [meta]
- quiver 2.1.3 [matcher meta]
- sky_engine 0.0.99
- source_span 1.7.0 [charcode collection meta path term_glyph]
- stack_trace 1.9.5 [path]
- string_scanner 1.0.5 [charcode meta source_span]
- term_glyph 1.1.0
- typed_data 1.2.0 [collection]
- vector_math 2.0.8
- xml 4.5.1 [collection convert meta petitparser]
- yaml 2.2.1 [charcode collection string_scanner source_span]

I have the same bug but if I hit the URL manually I get {}

Could we get an update on this issue ?

Similar error:
E/FirebaseCrashlytics(17407): Failed to retrieve settings from https://firebase-settings.crashlytics.com/spi/v2/platforms/android/gmp/1:496886502013:android:fa533748f802011bf19714/settings
Someone has a solution to this:
https://stackoverflow.com/questions/62196832/e-firebasecrashlytics-failed-to-retrieve-settings-from-https-firebase-setting

Same problem here with 17.2.1, one of my app flavours didnt't work throwing above error. Removing current apps and re-adding them in firebase project settings solved the problem for me.

I am facing too.

I have the same issue, I will try to remove the firebase project and start again

Similar error:
E/FirebaseCrashlytics(17407): Failed to retrieve settings from https://firebase-settings.crashlytics.com/spi/v2/platforms/android/gmp/1:496886502013:android:fa533748f802011bf19714/settings
Someone has a solution to this:
https://stackoverflow.com/questions/62196832/e-firebasecrashlytics-failed-to-retrieve-settings-from-https-firebase-setting

Same problem here with 17.2.1, one of my app flavours didnt't work throwing above error. Removing current apps and re-adding them in firebase project settings solved the problem for me.

I have the same issue, I will try to remove the app from the firebase project

That didn't work for me

Similar error:
E/FirebaseCrashlytics(17407): Failed to retrieve settings from https://firebase-settings.crashlytics.com/spi/v2/platforms/android/gmp/1:496886502013:android:fa533748f802011bf19714/settings
Someone has a solution to this:
https://stackoverflow.com/questions/62196832/e-firebasecrashlytics-failed-to-retrieve-settings-from-https-firebase-setting

Same problem here with 17.2.1, one of my app flavours didnt't work throwing above error. Removing current apps and re-adding them in firebase project settings solved the problem for me.

I am facing too and that didn't work for me

May be it's a 24 hours patience game or try the solution below:
Few changes made were:

Add implementation 'com.google.firebase:firebase-analytics:17.5.0'   implementation 'com.google.firebase:firebase-crashlytics:17.2.1' to app level gradle
Add classpath 'com.google.firebase:firebase-crashlytics-gradle:2.3.0' to android level gradle.
Add firebase_analytics to pubspec.yaml, this is just a fluke.
Rebuild the app code and do a force crash in the app. And after waiting for a minute or two, upon refreshing Crashlytics Dashboard I see...

May be it's a 24 hours patience game or try the solution below:
Few changes made were:
* Add `implementation 'com.google.firebase:firebase-analytics:17.5.0' implementation 'com.google.firebase:firebase-crashlytics:17.2.1'` to app level gradle

* Add `classpath 'com.google.firebase:firebase-crashlytics-gradle:2.3.0'` to android level gradle.

* Add `firebase_analytics` to pubspec.yaml, this is just a fluke.

* Rebuild the app code and do a force crash in the app. And after waiting for a minute or two, upon refreshing Crashlytics Dashboard I see...

I had a try to implement this solution, but it didn't work for me, unfortunately.
On the overview page of the Firebase project, I can see some past statistics from Crashlytics, but the Crushlytics console is not still available.

May be it's a 24 hours patience game or try the solution below:
Few changes made were:

Add implementation 'com.google.firebase:firebase-analytics:17.5.0' implementation 'com.google.firebase:firebase-crashlytics:17.2.1' to app level gradle
Add classpath 'com.google.firebase:firebase-crashlytics-gradle:2.3.0' to android level gradle.
Add firebase_analytics to pubspec.yaml, this is just a fluke.
Rebuild the app code and do a force crash in the app. And after waiting for a minute or two, upon refreshing Crashlytics Dashboard I see...

Thanks that work for me, but I need to call   FirebaseCrashlytics.instance.crash();
to make Crushlytics console available.
I'm getting a Crushlytics alert in the console about migrate to the newer sdk

Also, add apply plugin: 'com.google.firebase.crashlytics' to the bottom of the build.gradle of app level.

I made sure to follow all the instructions yet I am also experiencing this issue. The solution above did not work.

I'm meeting same problem now.
FirebaseCrashlytics(15078): Failed to retrieve settings from https://firebase-settings.crashlytics.com
I added respective plugin and classpath dependencies in native android , but it is not solved .

May be it's a 24 hours patience game or try the solution below:
Few changes made were:

Add implementation 'com.google.firebase:firebase-analytics:17.5.0' implementation 'com.google.firebase:firebase-crashlytics:17.2.1' to app level gradle
Add classpath 'com.google.firebase:firebase-crashlytics-gradle:2.3.0' to android level gradle.
Add firebase_analytics to pubspec.yaml, this is just a fluke.
Rebuild the app code and do a force crash in the app. And after waiting for a minute or two, upon refreshing Crashlytics Dashboard I see...

Thanks that work for me, but I need to call  FirebaseCrashlytics.instance.crash();
to make Crushlytics console available.
I'm getting a Crushlytics alert in the console about migrate to the newer sdk

(i try on emulator with google play, i was blocked since 1 week)
Do that, uninstall your app, flutter clean, install your app crash your app with FirebaseCrashlytics.instance.crash(); Then restart your app. Crashs are sent when app open again. You're firebase console will be unlocked.

@sulaysumaria
A new plugin version was rolled out yesterday, https://pub.dev/packages/firebase_crashlytics/changelog.
Please upgrade and try again to see if it works.
Thanks.

Similar to https://github.com/FirebaseExtended/flutterfire/issues/3676

For me it works, but with a new app created in Project Settings.
But it still does not for the old one.
What's interesting that the new store crash report to SQLite:

But the old one not:

All that I change is applicationId. The old one is com.mobile.k***y and the new one is com.mobile.k***y.dev

The error disappeared today on its own.
I still didn't manage to get to the dashboard, until I used an emulator with Google Services.

@sulaysumaria
A new plugin version was rolled out yesterday, https://pub.dev/packages/firebase_crashlytics/changelog.
Please upgrade and try again to see if it works.
Thanks.

I updated the plugin and the error persists.

pubspec.yaml

android/build.gradle

android/app/build.gradle

I updated the dependencies and the gradle files. Now I am getting following error:
[        ] E/AndroidRuntime(24741): java.lang.RuntimeException: Unable to get provider com.google.firebase.provider.FirebaseInitProvider: java.lang.IllegalStateException: The Crashlytics build ID is missing. This occurs when Crashlytics tooling is absent from your app's
build configuration. Please review Crashlytics onboarding instructions and ensure you have a valid Crashlytics account.
[   +1 ms] E/AndroidRuntime(24741): 	at android.app.ActivityThread.installProvider(ActivityThread.java:7318)
[        ] E/AndroidRuntime(24741): 	at android.app.ActivityThread.installContentProviders(ActivityThread.java:6778)
[        ] E/AndroidRuntime(24741): 	at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6628)
[        ] E/AndroidRuntime(24741): 	at android.app.ActivityThread.access$1700(ActivityThread.java:232)
[        ] E/AndroidRuntime(24741): 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1966)
[        ] E/AndroidRuntime(24741): 	at android.os.Handler.dispatchMessage(Handler.java:107)
[        ] E/AndroidRuntime(24741): 	at android.os.Looper.loop(Looper.java:214)
[        ] E/AndroidRuntime(24741): 	at android.app.ActivityThread.main(ActivityThread.java:7710)
[        ] E/AndroidRuntime(24741): 	at java.lang.reflect.Method.invoke(Native Method)
[        ] E/AndroidRuntime(24741): 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:516)
[        ] E/AndroidRuntime(24741): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:950)
[        ] E/AndroidRuntime(24741): Caused by: java.lang.IllegalStateException: The Crashlytics build ID is missing. This occurs when Crashlytics tooling is absent from your app's build configuration. Please review Crashlytics onboarding instructions and ensure you have
a valid Crashlytics account.
[   +2 ms] E/AndroidRuntime(24741): 	at com.google.firebase.crashlytics.internal.common.CrashlyticsCore.onPreExecute(CrashlyticsCore.java:123)
[        ] E/AndroidRuntime(24741): 	at com.google.firebase.crashlytics.FirebaseCrashlytics.init(FirebaseCrashlytics.java:165)
[        ] E/AndroidRuntime(24741): 	at com.google.firebase.crashlytics.CrashlyticsRegistrar.buildCrashlytics(CrashlyticsRegistrar.java:54)
[        ] E/AndroidRuntime(24741): 	at com.google.firebase.crashlytics.CrashlyticsRegistrar.access$lambda$0(Unknown Source:0)
[        ] E/AndroidRuntime(24741): 	at com.google.firebase.crashlytics.CrashlyticsRegistrar$$Lambda$1.create(Unknown Source:2)
[        ] E/AndroidRuntime(24741): 	at com.google.firebase.components.ComponentRuntime.lambda$new$0(com.google.firebase:firebase-components@@16.0.0:69)
[        ] E/AndroidRuntime(24741): 	at com.google.firebase.components.ComponentRuntime$$Lambda$1.get(Unknown Source:4)
[        ] E/AndroidRuntime(24741): 	at com.google.firebase.components.Lazy.get(com.google.firebase:firebase-components@@16.0.0:53)
[        ] E/AndroidRuntime(24741): 	at com.google.firebase.components.ComponentRuntime.initializeEagerComponents(com.google.firebase:firebase-components@@16.0.0:158)
[        ] E/AndroidRuntime(24741): 	at com.google.firebase.FirebaseApp.initializeAllApis(FirebaseApp.java:583)
[        ] E/AndroidRuntime(24741): 	at com.google.firebase.FirebaseApp.initializeApp(FirebaseApp.java:304)
[        ] E/AndroidRuntime(24741): 	at com.google.firebase.FirebaseApp.initializeApp(FirebaseApp.java:268)
[        ] E/AndroidRuntime(24741): 	at com.google.firebase.FirebaseApp.initializeApp(FirebaseApp.java:253)
[        ] E/AndroidRuntime(24741): 	at com.google.firebase.provider.FirebaseInitProvider.onCreate(FirebaseInitProvider.java:51)
[        ] E/AndroidRuntime(24741): 	at android.content.ContentProvider.attachInfo(ContentProvider.java:2154)
[        ] E/AndroidRuntime(24741): 	at android.content.ContentProvider.attachInfo(ContentProvider.java:2128)
[        ] E/AndroidRuntime(24741): 	at com.google.firebase.provider.FirebaseInitProvider.attachInfo(FirebaseInitProvider.java:45)
[        ] E/AndroidRuntime(24741): 	at android.app.ActivityThread.installProvider(ActivityThread.java:7307)
[        ] E/AndroidRuntime(24741): 	... 10 more

I was finally able to make it work.
Here is the configuration:
android/app/build.gradle:
apply plugin: 'com.android.application'
apply plugin: 'com.google.gms.google-services' <-- Add this
apply plugin: 'kotlin-android'
apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"
apply plugin: 'com.google.firebase.crashlytics' <-- Add this
...
dependencies {
    implementation 'com.google.firebase:firebase-analytics:17.5.0' <-- Add this
    implementation 'com.google.firebase:firebase-crashlytics:17.2.1' <-- Add this
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
}

gradle-wrapper.properties
#Fri Jun 23 08:50:38 CEST 2017
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-5.6.4-all.zip <-- Update this

android/build.gradle
    dependencies {
        classpath 'com.android.tools.build:gradle:3.5.0'
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
        classpath 'com.google.gms:google-services:4.3.4' <-- Add this
        classpath 'com.google.firebase:firebase-crashlytics-gradle:2.3.0' <-- Add this
    }

pubspec.yaml
firebase_crashlytics: 0.2.1
firebase_analytics: 6.0.1
firebase_core: 0.5.0

flutter doctor
[✓] Flutter (Channel stable, 1.22.0, on Mac OS X 10.15.7 19H2, locale en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 12.0.1)
[✓] Android Studio (version 4.0)
[✓] VS Code (version 1.49.2)
[✓] Connected device (1 available)

There are still a few issues that I faced. Maybe that is something firebase has to look at.

Crashes are not visible in real time. It took around half hour to show up on console.
When navigated to crashlytics from sidemenu, it shows the initial screen. But once I navigated to Project settings, and then to Crashlytics, it works fine.
Refreshing the crashlytics page goes to infinite loader.

I was finally able to make it work.
Here is the configuration:
android/app/build.gradle:
apply plugin: 'com.android.application'
apply plugin: 'com.google.gms.google-services' <-- Add this
apply plugin: 'kotlin-android'
apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"
apply plugin: 'com.google.firebase.crashlytics' <-- Add this
...
dependencies {
    implementation 'com.google.firebase:firebase-analytics:17.5.0' <-- Add this
    implementation 'com.google.firebase:firebase-crashlytics:17.2.1' <-- Add this
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
}

gradle-wrapper.properties
#Fri Jun 23 08:50:38 CEST 2017
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-5.6.4-all.zip <-- Update this

android/build.gradle
    dependencies {
        classpath 'com.android.tools.build:gradle:3.5.0'
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
        classpath 'com.google.gms:google-services:4.3.4' <-- Add this
        classpath 'com.google.firebase:firebase-crashlytics-gradle:2.3.0' <-- Add this
    }

pubspec.yaml
firebase_crashlytics: 0.2.1
firebase_analytics: 6.0.1
firebase_core: 0.5.0

flutter doctor
[✓] Flutter (Channel stable, 1.22.0, on Mac OS X 10.15.7 19H2, locale en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 12.0.1)
[✓] Android Studio (version 4.0)
[✓] VS Code (version 1.49.2)
[✓] Connected device (1 available)

There are still a few issues that I faced. Maybe that is something firebase has to look at.

Crashes are not visible in real time. It took around half hour to show up on console.
When navigated to crashlytics from sidemenu, it shows the initial screen. But once I navigated to Project settings, and then to Crashlytics, it works fine.
Refreshing the crashlytics page goes to infinite loader.

I agree, I got infinite loader on firebase crashlytics/analytics. Crashlytics is not realtime, it's weird....

After 5 days of trying to initialize crashlytics it finally started to work. I put google-services plugin below dependencies in android/app/build.gradle but it might be just a coincidence.
`dependencies {
implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
implementation 'com.google.firebase:firebase-analytics:17.5.0'
implementation 'com.google.firebase:firebase-crashlytics:17.2.1'
}
apply plugin: 'com.google.gms.google-services'
apply plugin: 'com.google.firebase.crashlytics'`
Remember to flutter clean -> flutter run if you want to try if this solution works for you.

Same issue
E/FirebaseCrashlytics(29887): Failed to retrieve settings from https://firebase-settings.crashlytics.com/spi/v2/platforms/android/gmp/1:504520051578:android:68a8cfa3ec789f666824c3/settings
android/build.gradle
dependencies {
        classpath 'com.android.tools.build:gradle:4.0.2'
        classpath 'com.google.gms:google-services:4.3.4'
        classpath 'com.google.firebase:firebase-crashlytics-gradle:2.3.0'
    }

android/app/build.gradle:
apply plugin: 'com.google.firebase.crashlytics'
apply plugin: 'com.google.gms.google-services'

I can't get this to work properly either. We use 2 different flavors. When running it locally it works for one flavor but it fails with the "Failed to retrieve settings..."-error for the other flavor. I already tried completely deleting the Firebase-project and using a new one but it still fails.
It does pick up the correct google-services.json because the project ID in the URL is correct. Also, the "Performance" tab already says "We detected that you've added the Firebase Performance Monitoring SDK" on the newly created project, so the Firebase integration in general seems to work.
I didn't see any additional errors with "adb logcat" either.

Not only is this issue quite a hassle but when it actually goes past this... then there's another problem with firestore security rules.
Did I miss a config or something?

It's working on me after update to new version
firebase_core: 0.5.0+1   firebase_crashlytics: ^0.2.1+1

It's working on me after update to new version
firebase_core: 0.5.0+1
firebase_crashlytics: ^0.2.1+1`

still not work for me. I hope they will fix this in near future

We're aware of this, looking to get a fix up asap.

Same error for me.

The issue is reproduced easily in a new project
event sent after app closed: {id: 0, progressId: null, message: Running "flutter pub get" in triage...}
event sent after app closed: {id: 0, progressId: null, finished: true}
Launching lib\main.dart on Android SDK built for x86 in debug mode...
Running Gradle task 'assembleDebug'...
√ Built build\app\outputs\flutter-apk\app-debug.apk.
Installing build\app\outputs\flutter-apk\app.apk...
Waiting for Android SDK built for x86 to report its views...
Debug service listening on ws://<IP_ADDRESS>:50966/Ma_iDxSvsrw=/ws
Syncing files to device Android SDK built for x86...
D/EGL_emulation(15165): eglMakeCurrent: 0xe61e6ec0: ver 2 0 (tinfo 0xe614d750)
D/eglCodecCommon(15165): setVertexArrayObject: set vao to 0 (0) 1 0
I/OpenGLRenderer(15165): Davey! duration=770ms; Flags=1, IntendedVsync=12878198007722, Vsync=12878198007722, OldestInputEvent=9223372036854775807, NewestInputEvent=0, HandleInputStart=12878202388100, AnimationStart=12878202463000, PerformTraversalsStart=12878202487700, DrawStart=12878885909100, SyncQueued=12878886494900, SyncStart=12878888086500, IssueDrawCommandsStart=12878888616100, SwapBuffers=12878901239300, FrameCompleted=12878969629300, DequeueBufferDuration=35075000, QueueBufferDuration=510000,
I/Choreographer(15165): Skipped 46 frames!  The application may be doing too much work on its main thread.
E/FirebaseInstanceId(15165): binding to the service failed
E/FirebaseCrashlytics(15165): Failed to retrieve settings from https://firebase-settings.crashlytics.com/spi/v2/platforms/android/gmp/1:517361392592:android:c4c29c35e54ab5841db7d5/settings
D/EGL_emulation(15165): eglMakeCurrent: 0xf127f460: ver 2 0 (tinfo 0xc6276570)
D/eglCodecCommon(15165): setVertexArrayObject: set vao to 0 (0) 1 0

buildscript {
    ext.kotlin_version = '1.3.50'
    repositories {
        google()
        jcenter()
    }

    dependencies {
        classpath 'com.android.tools.build:gradle:3.5.0'
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
        classpath 'com.google.gms:google-services:4.3.4'
        classpath 'com.google.firebase:firebase-crashlytics-gradle:2.2.0'

    }
}

dependencies {
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
    implementation 'com.google.firebase:firebase-analytics'
}
apply plugin: 'com.google.gms.google-services'
apply plugin: 'com.google.firebase.crashlytics'

flutter doctor -v
[✓] Flutter (Channel stable, 1.22.0, on Microsoft Windows [Version 10.0.19041.508], locale en-US)
    • Flutter version 1.22.0 at C:\Code\flutter_stable
    • Framework revision d408d302e2 (10 days ago), 2020-09-29 11:49:17 -0700
    • Engine revision 5babba6c4d
    • Dart version 2.10.0

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at C:\Code\sdk
    • Platform android-30, build-tools 30.0.2
    • ANDROID_HOME = C:\Code\sdk
    • Java binary at: C:\Code\android-studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[✓] Android Studio (version 4.0)
    • Android Studio at C:\Code\android-studio
    • Flutter plugin version 50.0.1
    • Dart plugin version 193.7547
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[✓] VS Code (version 1.50.0)
    • VS Code at C:\Users\Taha\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.15.0

[✓] Connected device (1 available)
    • Android SDK built for x86 (mobile) • emulator-5554 • android-x86 • Android 10 (API 29) (emulator)

• No issues found!

  firebase_core: "^0.5.0+1"
  firebase_crashlytics: ^0.2.1+1

I had this all day yesterday, it seemed to work by fluke after around 16 hours. I've attempted to recreate the scenarios so far without success... (WIP)

Google ClassPath
Crashlytics ClassPath
Crashlytics Implementation
Analytics Implementation
Plugins At Bottom
Status

com.google.gms:google-services:4.3.4
com.google.firebase:firebase-crashlytics-gradle:2.2.0
com.google.firebase:firebase-crashlytics:17.2.2
com.google.firebase:firebase-analytics:17.6.0
No
Failed

I was finally able to make it work.
Here is the configuration:
android/app/build.gradle:
apply plugin: 'com.android.application'
apply plugin: 'com.google.gms.google-services' <-- Add this
apply plugin: 'kotlin-android'
apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"
apply plugin: 'com.google.firebase.crashlytics' <-- Add this
...
dependencies {
    implementation 'com.google.firebase:firebase-analytics:17.5.0' <-- Add this
    implementation 'com.google.firebase:firebase-crashlytics:17.2.1' <-- Add this
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
}

gradle-wrapper.properties
#Fri Jun 23 08:50:38 CEST 2017
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-5.6.4-all.zip <-- Update this

android/build.gradle
    dependencies {
        classpath 'com.android.tools.build:gradle:3.5.0'
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
        classpath 'com.google.gms:google-services:4.3.4' <-- Add this
        classpath 'com.google.firebase:firebase-crashlytics-gradle:2.3.0' <-- Add this
    }

pubspec.yaml
firebase_crashlytics: 0.2.1
firebase_analytics: 6.0.1
firebase_core: 0.5.0

flutter doctor
[✓] Flutter (Channel stable, 1.22.0, on Mac OS X 10.15.7 19H2, locale en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 12.0.1)
[✓] Android Studio (version 4.0)
[✓] VS Code (version 1.49.2)
[✓] Connected device (1 available)

There are still a few issues that I faced. Maybe that is something firebase has to look at.

Crashes are not visible in real time. It took around half hour to show up on console.
When navigated to crashlytics from sidemenu, it shows the initial screen. But once I navigated to Project settings, and then to Crashlytics, it works fine.
Refreshing the crashlytics page goes to infinite loader.

Thank you

This work for me
for project level
buildscript {
dependencies {
    classpath 'com.android.tools.build:gradle:3.5.0'

    classpath 'com.google.gms:google-services:4.3.3'

    classpath 'com.google.firebase:firebase-crashlytics-gradle:2.3.0'
}

}
for module level
apply plugin: 'com.android.application'
apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"
apply plugin: 'com.google.firebase.crashlytics'
dependencies{
implementation 'com.google.firebase:firebase-analytics:17.5.0'
implementation 'com.google.firebase:firebase-crashlytics:17.2.2'
}
apply plugin: 'com.google.gms.google-services'
If your crash in flutter not working, make it crash in native android app.

This work for me
for flutter
in pubspec.yaml
firebase_crashlytics: ^0.2.1
in native android
for project level
buildscript {
dependencies {
    classpath 'com.android.tools.build:gradle:3.5.0'

    classpath 'com.google.gms:google-services:4.3.3'

    classpath 'com.google.firebase:firebase-crashlytics-gradle:2.3.0'
}

}
for module level
apply plugin: 'com.android.application'
apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"
apply plugin: 'com.google.firebase.crashlytics'
dependencies{
implementation 'com.google.firebase:firebase-analytics:17.5.0'
implementation 'com.google.firebase:firebase-crashlytics:17.2.2'
}
apply plugin: 'com.google.gms.google-services'
If your crash in flutter not working, make it crash in native android app.

Thanks. It's working. But, you forget to add plugin firebase_core in pubspec.yaml.
Flutter, in pubspec.yaml
firebase_crashlytics: ^0.2.1
firebase_core: ^0.5.0

work for me out of nowhere. I think if we sure everything is in the right place, we just have to wait 16-24 hours so that crashlytic dashboard becomes enabled.

I also tried in a lot of constellations (versions) and i didnt get it work on android. iOS works like a charm.
here some log output of my last try, with overridden version (17.2.1) of crashlytics
10-12 15:53:29.000 14628 14628 D FirebaseCrashlytics: Crashlytics completed exception processing. Invoking default exception handler.
10-12 17:23:27.384 16386 16386 D FirebaseCrashlytics: Crashlytics automatic data collection ENABLED by API.
10-12 17:23:27.389 16386 16386 D FirebaseCrashlytics: Firebase Analytics is available.
10-12 17:23:27.395 16386 16386 D FirebaseCrashlytics: Firebase Analytics listener registered successfully.
10-12 17:23:27.414 16386 16386 D FirebaseCrashlytics: Reading cached settings...
10-12 17:23:27.415 16386 16386 D FirebaseCrashlytics: No cached settings found.
10-12 17:23:27.415 16386 16386 D FirebaseCrashlytics: No cached settings data found.
10-12 17:23:27.420 16386 16386 D FirebaseCrashlytics: Mapping file ID is:<PHONE_NUMBER>0000000000000000000000
10-12 17:23:27.420 16386 16386 I FirebaseCrashlytics: Initializing Crashlytics 17.2.1
10-12 17:23:27.423 16386 16386 D FirebaseCrashlytics: Installer package name is: null
10-12 17:23:27.533 16386 16386 D FirebaseCrashlytics: Exception handling initialization successful
10-12 17:23:27.558 16386 16410 D FirebaseCrashlytics: Found matching FID, using Crashlytics IID: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
10-12 17:23:27.559 16386 16410 D FirebaseCrashlytics: Opening a new session with ID XXXXXXXXXXXX-XXXX-XXXX-XXXXXXXXXXXX
10-12 17:23:27.648 16386 16410 D FirebaseCrashlytics: Initialization marker file created.
10-12 17:23:27.649 16386 16410 D FirebaseCrashlytics: Registered Firebase Analytics event receiver for breadcrumbs
10-12 17:23:27.650 16386 16410 D FirebaseCrashlytics: Finalizing previously open sessions.
10-12 17:23:27.682 16386 16410 D FirebaseCrashlytics: Closing open sessions.
10-12 17:23:27.682 16386 16410 D FirebaseCrashlytics: Closing session: XXXXXXXXXXXX-XXXX-XXXX-XXXXXXXXXXXX
10-12 17:23:27.682 16386 16410 D FirebaseCrashlytics: Collecting session parts for ID XXXXXXXXXXXX-XXXX-XXXX-XXXXXXXXXXXX
10-12 17:23:27.683 16386 16410 D FirebaseCrashlytics: Session XXXXXXXXXXXX-XXXX-XXXX-XXXXXXXXXXXX has fatal exception: false
10-12 17:23:27.698 16386 16410 D FirebaseCrashlytics: Session XXXXXXXXXXXX-XXXX-XXXX-XXXXXXXXXXXX has non-fatal exceptions: false
10-12 17:23:27.699 16386 16410 D FirebaseCrashlytics: No events present for session ID XXXXXXXXXXXX-XXXX-XXXX-XXXXXXXXXXXX
10-12 17:23:27.699 16386 16410 D FirebaseCrashlytics: Removing session part files for ID XXXXXXXXXXXX-XXXX-XXXX-XXXXXXXXXXXX
10-12 17:23:27.704 16386 16410 D FirebaseCrashlytics: Closed all previously open sessions
10-12 17:23:27.706 16386 16410 D FirebaseCrashlytics: Unsent reports are available.
10-12 17:23:27.707 16386 16410 D FirebaseCrashlytics: Crashlytics automatic data collection ENABLED by API.
10-12 17:23:27.707 16386 16410 D FirebaseCrashlytics: Automatic data collection is enabled. Allowing upload.
10-12 17:23:27.711 16386 16410 D FirebaseCrashlytics: Initialization marker file removed: true
10-12 17:23:28.360 16386 16411 D FirebaseCrashlytics: Received Analytics message: 3 Bundle[{params=Bundle[{_o=auto, _sid=XXXXXXXXXX}], name=_s, timestampInMillis=1602516208013}]
10-12 17:23:28.602 16386 16410 D FirebaseCrashlytics: Checking for crash reports...
10-12 17:23:28.631 16386 16410 D FirebaseCrashlytics: Found crash report /data/user/0/com.example.test_crashlyitcs_app/files/.com.google.firebase.crashlytics/fatal-sessions/XXXXXXXXXXXX-XXXX-XXXX-XXXXXXXXXXXX.cls
10-12 17:23:28.669 16386 16410 D FirebaseCrashlytics: Reports are being sent.
10-12 17:23:28.796 16386 16411 D FirebaseCrashlytics: Received Analytics message: 3 Bundle[{params=Bundle[{_o=auto, _sc=MainActivity, _si=-XXXXXXXXXXXXXXXXXXX}], name=_vs, timestampInMillis=1602516208610}]
10-12 17:23:28.800 16386 16414 D FirebaseCrashlytics: Requesting settings from https://firebase-settings.crashlytics.com/spi/v2/platforms/android/gmp/1:XXXXXXXXXXXX:android:XXXXXXXXXXXXXXXXXXXXXX/settings
10-12 17:23:28.800 16386 16414 D FirebaseCrashlytics: Settings query params were: {instance=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX, build_version=1, display_version=1.0.0, source=1}
10-12 17:23:29.449 16386 16414 D FirebaseCrashlytics: Settings request ID: null
10-12 17:23:29.449 16386 16414 D FirebaseCrashlytics: Settings result was: 403
10-12 17:23:29.451 16386 16414 E FirebaseCrashlytics: Failed to retrieve settings from https://firebase-settings.crashlytics.com/spi/v2/platforms/android/gmp/1:XXXXXXXXXXXX:android:XXXXXXXXXXXXXXXXXXXXXX/settings
c10-12 18:27:27.002 16386 16386 D FirebaseCrashlytics: Crashlytics is handling uncaught exception "io.flutter.plugins.firebase.crashlytics.FirebaseCrashlyticsTestCrash: This is a test crash caused by calling .crash() in Dart." from thread main
10-12 18:27:31.007 16386 16386 D FirebaseCrashlytics: Crashlytics completed exception processing. Invoking default exception handler.

I followed the official docs to upgrade/install crashlytics:
https://firebase.flutter.dev/docs/installation/android
https://firebase.flutter.dev/docs/core/usage
https://firebase.flutter.dev/docs/crashlytics/usage
I have also waited more than 24 hours on several projects to see if the Crashlytics console would work, but it didn't work

Make sure to add this :
await Firebase.initializeApp();
await FirebaseCrashlytics.instance.setCrashlyticsCollectionEnabled(true);

@EArminjon i also initialized the app in a FutureBuilder and i waited to be instantiated before executing the test crash.
This line of code is not really necessary because by default collection is enabled.
await FirebaseCrashlytics.instance.setCrashlyticsCollectionEnabled(true);

I was finally able to make it work.
Here is the configuration:
android/app/build.gradle:
apply plugin: 'com.android.application'
apply plugin: 'com.google.gms.google-services' <-- Add this
apply plugin: 'kotlin-android'
apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"
apply plugin: 'com.google.firebase.crashlytics' <-- Add this
...
dependencies {
    implementation 'com.google.firebase:firebase-analytics:17.5.0' <-- Add this
    implementation 'com.google.firebase:firebase-crashlytics:17.2.1' <-- Add this
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
}

gradle-wrapper.properties
#Fri Jun 23 08:50:38 CEST 2017
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-5.6.4-all.zip <-- Update this

android/build.gradle
    dependencies {
        classpath 'com.android.tools.build:gradle:3.5.0'
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
        classpath 'com.google.gms:google-services:4.3.4' <-- Add this
        classpath 'com.google.firebase:firebase-crashlytics-gradle:2.3.0' <-- Add this
    }

pubspec.yaml
firebase_crashlytics: 0.2.1
firebase_analytics: 6.0.1
firebase_core: 0.5.0

flutter doctor
[✓] Flutter (Channel stable, 1.22.0, on Mac OS X 10.15.7 19H2, locale en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 12.0.1)
[✓] Android Studio (version 4.0)
[✓] VS Code (version 1.49.2)
[✓] Connected device (1 available)

There are still a few issues that I faced. Maybe that is something firebase has to look at.
* Crashes are not visible in real time. It took around half hour to show up on console.

* When navigated to crashlytics from sidemenu, it shows the initial screen. But once I navigated to Project settings, and then to Crashlytics, it works fine.

* Refreshing the crashlytics page goes to infinite loader.

This solution avoid the "Failed to retrieve settings from ..." error, but Crashlytics still not connected.

I was finally able to make it work.
Here is the configuration:
android/app/build.gradle:
apply plugin: 'com.android.application'
apply plugin: 'com.google.gms.google-services' <-- Add this
apply plugin: 'kotlin-android'
apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"
apply plugin: 'com.google.firebase.crashlytics' <-- Add this
...
dependencies {
    implementation 'com.google.firebase:firebase-analytics:17.5.0' <-- Add this
    implementation 'com.google.firebase:firebase-crashlytics:17.2.1' <-- Add this
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
}

gradle-wrapper.properties
#Fri Jun 23 08:50:38 CEST 2017
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-5.6.4-all.zip <-- Update this

android/build.gradle
    dependencies {
        classpath 'com.android.tools.build:gradle:3.5.0'
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
        classpath 'com.google.gms:google-services:4.3.4' <-- Add this
        classpath 'com.google.firebase:firebase-crashlytics-gradle:2.3.0' <-- Add this
    }

pubspec.yaml
firebase_crashlytics: 0.2.1
firebase_analytics: 6.0.1
firebase_core: 0.5.0

flutter doctor
[✓] Flutter (Channel stable, 1.22.0, on Mac OS X 10.15.7 19H2, locale en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 12.0.1)
[✓] Android Studio (version 4.0)
[✓] VS Code (version 1.49.2)
[✓] Connected device (1 available)

There are still a few issues that I faced. Maybe that is something firebase has to look at.
* Crashes are not visible in real time. It took around half hour to show up on console.

* When navigated to crashlytics from sidemenu, it shows the initial screen. But once I navigated to Project settings, and then to Crashlytics, it works fine.

* Refreshing the crashlytics page goes to infinite loader.

This solution avoid the "Failed to retrieve settings from ..." error, but Crashlytics still not connected.

@roger357 this solution also for me didn't work

I finally got it to work by strictly following the flutterfire instructions, and adding the dependencies to app/build.gradle:
dependencies {
implementation 'com.google.firebase: firebase-analytics: 17.6.0'
implementation 'com.google.firebase: firebase-crashlytics: 17.2.2'
}
and the most important thing for me: move at the end of the file:
apply plugin: 'com.google.firebase.crashlytics'
(before the google-services plugin)

i tried everything, none of them worked.
Failed to retrieve settings from https://firebase-settings.crashlytics.com/spi/v2/platforms/android/gmp/1:349507000736:android:d5c78891b87bff31d9ecc5/settings
android/gradle
    dependencies {
        classpath 'com.google.gms:google-services:4.3.4'
        classpath 'com.google.firebase:firebase-crashlytics-gradle:2.3.0'
    }

app/gradle
apply plugin: 'com.google.firebase.crashlytics'
apply plugin: 'com.google.gms.google-services'

dependencies {
    implementation 'com.google.firebase:firebase-analytics:17.6.0'
    implementation 'com.google.firebase:firebase-crashlytics:17.2.2'
}

pubspec.yaml
  firebase_core: ^0.5.0+1
  firebase_crashlytics: ^0.2.1+1

I observed the issue is only present in the android emulator, on the iOS platform, iOS integration and testing on the iphone emulator worked perfectly. Then I deployed the android application to the closed-beta track in the playstore and crashed the app in the real device environment, after a short duration, logs appeared correctly without any trouble.

I am also experiencing this issue. Using the latest version of everything. I've tried every suggestion from this issue. I still get "Failed to retrieve settings..."

Hi,
I am also getting this error,
E/FirebaseCrashlytics(29192): Failed to retrieve settings from https://firebase-settings.crashlytics.com/spi/v2/platforms/android/gmp

Initial PR added, works consistently through local testing. Please follow the link and follow the steps through the preview documentation.
Any and feedback welcome

Hello and thank you @dackers86 .
"Failed to retrieve settings ..." message is out, but crashlytics console no detect crashes. Crash was forced with FirebaseCrashlytics.instance.crash();

Initial PR added, works consistently through local testing. Please follow the link and follow the steps through the preview documentation.
Any and feedback welcome

its worked for me.

Hi @roger357.
Can you confirm which version of firebase_core you are using?

Hi @roger357.
Can you confirm which version of firebase_core you are using?

Hi @dackers86.
I'm using this firebase_core: ^0.5.0+1

sorry I don't saw the Firebase_core version change, I'm changing to firebase_crashlytics: ^0.2.1+1.
Testing....

Thanks.
Could you try firebase_core: ^0.5.0. Bit of guesswork, but this specific config has hard to pin down!

Latest testing was based on version firebase_crashlytics: "^0.2.1+1"

@dackers86 I have the same problem and I'm using firebase_crashlytics: "^0.2.1+1". would you please help to fix it?

@roger357 @samin-fs When working through the above docs i'd make sure to do the following....
flutter clean && flutter run - only on the initial changes.
Then 'flutter' to re-run the app with the expected crashes.
Also when using the emulator. Make sure uninstall the app from the device before rebuilding.
Apologies if this isn't comprehensive, it took a while to produce initial consistent installations.
Any additional feedback is welcome

Hello @dackers86,
I'm trying with the follow configuration
pubspec.yml
  firebase_core: ^0.5.0

  firebase_auth: ^0.18.1+2

  firebase_analytics: ^6.0.2

  firebase_crashlytics: "^0.2.1+1"

Gradle:
android/build.gradle
    dependencies {
        // Other dependencies
        classpath 'com.google.gms:google-services:4.3.3'  // Google Services plugin
        classpath 'com.google.firebase:firebase-crashlytics-gradle:2.3.0'
    }

android/app/build.gradle
dependencies {
    // Other dependencies
    implementation platform('com.google.firebase:firebase-bom:25.12.0')
    implementation 'com.google.firebase:firebase-analytics'
}

apply plugin: 'com.google.gms.google-services'  // Google Services plugin
apply plugin: 'com.google.firebase.crashlytics'

The initial message "Failed to retrieve settings ..." still out. But Firebase Crashlytics Console not connect after app crash (forced).
Thank you in advance.

Initial PR added, works consistently through local testing. Please follow the link and follow the steps through the preview documentation.
Any and feedback welcome

My configuration based on this link is not working unforunately.
I've also tried adding firebase_analytics: ^6.0.2 but that didn't worked either.
Let me know if you have any idea how to fix that. Maybe waiting 24 hours would be enough for it to start working?
My configuration:
pubspec.yml

firebase_crashlytics: 0.2.1+1
firebase_core: 0.5.0+1

Gradle:
android/build.gradle

classpath 'com.google.gms:google-services:4.3.3'
classpath 'com.google.firebase:firebase-crashlytics-gradle:2.3.0'

android/app/build.gradle

implementation platform('com.google.firebase:firebase-bom:25.12.0')
implementation 'com.google.firebase:firebase-analytics'

@snowb1shop @samin-fs
I've been attempting to recreate this morning. Does the issue still exist, I've noticed this morning that the app is initialising even without manually causing a crash?

It started to work, thank you!

I've tried almost all solution provided here, my config still doens't work.

Still not working with
  firebase_core: "0.5.0"
  firebase_analytics: "^6.0.1"
  firebase_crashlytics: "^0.2.1"

@Nico04 @Valentin-Seehausen
Would it be possible to create a test app with flutter create testApp.
This works consistently for new apps, i'm wondering it could be some other configuration?

@Nico04 @Valentin-Seehausen
Would it be possible to create a test app with flutter create testApp.
This works consistently for new apps, i'm wondering it could be some other configuration?

I've tried that, but it also failed for me 😔

After creating a new project in firebase and adding configs from https://firebase.google.com/docs/crashlytics/get-started?hl=en&authuser=0&platform=android it worked. Don't know if this is an satisfying solution.

@dackers86 i noticed that this problem only happens on the emulator and it's working fine on a real device, thank you.

This issue might be a good read for anyone experiencing this issue:
https://github.com/firebase/firebase-android-sdk/issues/1944
Specifically this comment:
https://github.com/firebase/firebase-android-sdk/issues/1944#issuecomment-706385711
It looks like on Android they have migrated the crash uploading mechanism to JobScheduler and it schedules automatically to 1 second after the crash. The thing is JobScheduler has no guarantees, you might schedule it to run after one second but the system will instead opt for it to run 15 or even 30 minutes later. I was able to see this in some of my own logs:
Scheduled for 1000ms later:
10-20 15:02:41.651 13633 13728 D TransportRuntime.JobInfoScheduler: Scheduling upload for context TransportContext(cct, HIGHEST, MSRodHRwczovL2NyYXNobHl0aWNzcmVwb3J0cy1wYS5nb29nbGVhcGlzLmNvbS92MS9maXJlbG9nL2xlZ2FjeS9iYXRjaGxvZ1xBSXphU3lCcnBTWVQ0RkZMMDlyZUhKaTZIOUZZZGVpU25VVE92Mk0=) with jobId=-354078233 in 1000ms(Backend next call timestamp<PHONE_NUMBER>011). Attempt 1

Scheduled for 488293ms later:
10-21 11:19:01.061  6765  6793 D TransportRuntime.JobInfoScheduler: Scheduling upload for context TransportContext(cct, HIGHEST, MSRodHRwczovL2NyYXNobHl0aWNzcmVwb3J0cy1wYS5nb29nbGVhcGlzLmNvbS92MS9maXJlbG9nL2xlZ2FjeS9iYXRjaGxvZ1xBSXphU3lCcnBTWVQ0RkZMMDlyZUhKaTZIOUZZZGVpU25VVE92Mk0=) with jobId=-1113639633 in 488293ms(Backend next call timestamp<PHONE_NUMBER>354). Attempt 1

In the end I was able to see the crashes in my dashboard around 5 minutes after all of this, because the first attempt above was uploaded successfully. I mostly followed @dackers86 guide, except the BOM dependencies. The key points for me were:

Re-opening the app after forcing the crash(I suggest just tapping the app's icon to open it directly without flutter run)
Checking the timestamps in logcat to make sure there is no JobScheduler delays and to confirm the upload has finished(this is discussed in the comment I linked above).
Create a button in your settings menu that only shows in debug builds that can mock a crash(and calls FirebaseCrashlytics.instance.crash).

I suggest the last point about the button because it is written in the iOS/Android documentation. I have a feeling running flutter run consecutively might be causing issues but I can't confirm this it's just a hunch. There's a lot of factors in play here.

I should probably also add that in the iOS documentation it tells you to create a button, start the app in XCode an then stop the app and re-open it directly without XCode. This has something to do with XCode's debugger interfering with Crashlytics(I have no idea if this applies to flutter run too. It also specifically tells you to change your Debug Information Format to 'DWARF with dSYM File'.

What fixed the issue for me is updating the google-services.json file after enabling crashlytics for the app. There was an issue with the  mobilesdk_app_id in old and new service.json files.

It appears the OP was able to resolve the problem. We have also updated the documentation here to ensure you have properly configured your app. Please reopen a new issue if you've update to the latest major version, followed the updated docs closely, and you're still getting an error.


Support parameter substitution for resolver params

Changes
Part of #4710
Until we do v1beta1 of ResolutionRequest, it will still have parameters of map[string]string, so we're only doing limited substitution.
/kind feature
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[ ] Has Docs included if any changes are user facing
[x] Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[x] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
[ ] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
NONE

/assign @lbernick @jerop @vdemeester @dibyom

I'm a bit confused-- we're allowing substitution of array and object params in resolver ref, but when they're passed to the resolution request we can only do string params? it seems like it would make more sense to not allow array and object params in resolver ref if we can't pass them to resolution request.

Yeah, I'm planning to add support for array/object params to ResolutionRequest in v1beta1, so I debated whether to block them for now or just shrug and only pass on strings. I opted for the latter, since it's fairly short term, but am willing to be persuaded. =)

what's the timeline for v1beta1? if v1beta1 resolutionrequest won't be in the same release I'd definitely say reject. If they'll be in the same release it would still be good for the commit to be self consistent, but I wouldn't push back as much

So resolution will be fully merged for v0.40, but I plan to let it wait til v0.42 (in November) for v1beta1 to give it a month in the wild to make sure no critical issues pop up. I'll rework this to reject array/object params shortly.

@lbernick Updated!


[BUG] - TableHeader and TableBody typing error

NextUI Version
2.4.2
Describe the bug
TableHeader and TableBody can not handle condition rendering like below:

Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
<Table aria-label={"Example Table"}>
    <TableHeader>
	{(props.actions && <TableColumn key={"action"}>Do Some Action</TableColumn>)}
    </TableHeader>
    <TableBody>
	{(props.actions && <TableCell key={"action"}>{props.actions}</TableCell>)}
    </TableBody>
</Table>

Expected behavior
The idea here is to write a Table wrapper that supports pass in customizable, optional row actions like delete, edit, copy, etc...
Is this kind of usage can only achieved by using Dynamic in NextUI's Doc? If so, I think it's a little redundant:
for common usage, we pass a headers to render the TableColumn in TableHeader. If a actions is passed, that means we have to create a local variable, let's say, totalHeaders to contain both the props.actions header and props.header, code example below:
function TableTest(props: {headers: SomeHeader[], actions?: ReactNode}) {
    // I don't know if useState's initial value set to props value is correct, feel free to point me out ^_^
    const [totalHeaders, setTotalHeaders] = useState<SomeHeader[]>([props.headers])

  useEffect(() => {
    if (props.actions) {
        // unpack the previous array and append a new actionHeader with its type is `SomeHeader`
        setTotalHeaders(prev => [...prev, actionHeader])
    }
  }, [])

    return (
    // Table here, headers are used like <TableHeader columns={totalHeaders}/>
    )
}

If my "redundant" thought is wrong, please correct me and explain. Right now I will find a way to use Dynamic
Screenshots or Videos
No response
Operating System Version
macOS
Browser
Chrome

Table is a collection-based component. Empty children is not allowed and your code could produce empty children. What you can do is something like this
<TableHeader>
  {condition ? (
    // your TableColumn to be shown if the condition is true
  ) : (
    // a hidden TableColumn so that there is at least one child
  )}
</TableHeader>


IoTCLI kafka bridge generates unreachable route

When running the command:
IoTCLI kafka bridge

The following route is created:
oc get route
NAME                      HOST/PORT      PATH   SERVICES                   PORT   TERMINATION   WILDCARD
my-bridge-ingress-bfmdl   my-bridge.io   /      my-bridge-bridge-service   8080                 None

This is not a reachable route in my cluster. This is probably only reachable in a cluster based in this domain.

So sometimes it just takes a bit for the user to be generated after installation, I am going to try and make a self checking mechanism in the ceph setup command

Right, so currently for the http bridge we are using a K8's ingress rather then a route which is why the can be as shown, but as long as the bridge health checks are good  ->
curl -v GET http://my-bridge.io/healthy
Should return
> GET /healthy HTTP/1.1
> Host: my-bridge.io:80
> User-Agent: curl/7.61.1
> Accept: */*
>
< HTTP/1.1 200 OK
< content-length: 0

and it accepts a post with some junk
curl -X POST \
  http://my-bridge.io/topics/my-topic \
  -H 'content-type: application/vnd.kafka.json.v2+json' \
  -d '{
    "records": [
        {
            "key": "key-1",
            "value": "value-1"
        },
        {
            "key": "key-2",
            "value": "value-2"
        }
    ]
}'

Should return
{
   "offsets":[
      {
         "partition":0,
         "offset":0
      },
      {
         "partition":0,
         "offset":1
      }
   ]
}

Then It should be alright , If you see the following
* Could not resolve host: GET
* Closing connection 0
curl: (6) Could not resolve host: GET
* Could not resolve host: my-bridge.io
* Closing connection 1
curl: (6) Could not resolve host: my-bridge.io

Then something is incorrect with the local DNS routing in your hosts file
We are also in the process of converting the Ingress to a Route but will keep the Documentation current If so.  Please let me know if you have any other issues with the bridge

@astoycos I'm confused. I'm deploying into an OCP cluster in AWS commercial from my laptop at home. I'm not sure how my laptop using Verizon's DNS would know how to send traffic to my-bridge.io and route that to my cluster. Are you suggesting that these commands should be run from a cluster hosts? Not sure how to do that with RHCOS.

Ok cool, so we are working with openshift on openstack on PSI infrastructure and can manually route our DNS with our hosts file but we are going to transition to a route and that should fix your issues. I will work on that today @dmc5179

We definitely do not want you to have to run from a cluster hosts though! :)

Fixed this as well @dmc5179, we transitioned from using a k8's ingress to a route, fix will be in latest release once the Ceph versioning bugs are worked out

fixed with latest Release


Need IPv6 Masternodes

https://github.com/TrustPlus/TRUSTplusXTP/blob/bcd9e4acb200808c51bfde3707c7544bf26b88bd/src/activemasternode.cpp#L159

From what I can tell on Dash, it’s either IPv4 or IPv6.


[BUG] Delta Location on local mode is incorrect

Bug
Describe the problem
When creating a delta table specifying the location on spark local the delta_log files appear on the proper path but the table is registered in the metastore with a prefix to the path!
Steps to reproduce
Here is a sample sbt project: https://github.com/adrianabreu/delta-1.1.0-table-location-error-example/blob/master/src/test/scala/example/HelloSpec.scala
    val spark = SparkSession
    .builder()
    .enableHiveSupport()
    .master("local")
    .appName("test-session")
    .getOrCreate()

    spark.sql("""CREATE DATABASE IF NOT EXISTS bronze""")
    spark.sql("""CREATE TABLE bronze.users (
    |  name string,
    |  active boolean
    |)
    |USING delta
    |LOCATION 'spark-warehouse/users'""".stripMargin)

Observed results
The table location in the metastore is registered as:
spark-warehouse/bronze.db/spark-warehouse/users
Expected results
The table location should be: spark-warehouse/users
Further details
When no db is specified it works as expected
Environment information

Delta Lake version: 1.1.0
Spark version: 3.2.1
Scala version: 2.12

Willingness to contribute
The Delta Lake Community encourages bug fix contributions. Would you or another member of your organization be willing to contribute a fix for this bug to the Delta Lake code base?

[ ] Yes. I can contribute a fix for this bug independently.
[X] Yes. I would be willing to contribute a fix for this bug with guidance from the Delta Lake community.
[ ] No. I cannot contribute a bug fix at this time.

You may need to specify an absolute path for location, in Spark

If it is an absolute path, it represents the real Warehouse
If it is a relative path, the path is appended after the real Warehouse

@yikf Looks like it is working as expected? Need to be given an absolute path. Please reopen, if there are any remaining issues here.


Cache the sidebar nav

Caches the nav partials as one fragment, keyed by user_status_string.

admin_mode
browser.bot?
logged_in
no_user

Should wait for #1821.

coverage: 94.607% (+0.002%) from 94.605%
when pulling 82ac4abf1f6364fe77bd95feac044bba44ce1714 on nimmo-cache-try2
into f470bbb5e02f7bdcfdc0d90721095e058963bc8a on main.

Yes, this could really use reorganization, and I like doing it in small steps.
It''s generally great. I love the idea of a reduced sidebar for anonymous users.
Some comments re News

Since News was removed from the home page, it's become a less effective way of communicating with users.
Non logged in users should have a link to the News indiex.
Maybe remove News from the Index area, and put it at the top (for both logged in and non-logged in users).

@JoeCohen as you probably noticed I made your requested "News" changes on #1820, good idea.
Let me know if you want to play with this caching setup. The relevant test is to log in as two different users in two different browsers, on development, and check that the navbar knows who you are in both cases. (You can only test that by shrinking your browser window, because currently the user menu only displays in the sidebar on mobile.)
It's conceivable we could write a system test that tests that using two different sessions, but i'm more interested to check if the cache makes any difference on the server. I don't think the test environment is set up to use the cache in any case.


Updated Package.Json

Fixed Natik making himself supreme leader of the server, and detailed more of the split of clubs from the main website.

@nsinha0 won't be happy about this 😜


HTTPError 307

I don't understand why...

d = feedparser.parse('https://www2.yggtorrent.gg/rss?action=generate&type=cat&id=2145')
d
{'bozo': 1, 'entries': [], 'feed': {}, 'bozo_exception': <HTTPError 307: 'The HTTP server returned a redirect error that would lead to an infinite loop.\nThe last 30x error message was:\nTemporary Redirect'>}

feedparser.parse does NOT fetch the feed it will ONLY parse the text.  You have to fetch the feed text first with our HTTP library of choice. Cheers. Prost.

The error message is very strange for that though.

FYI: Double checking your error - you are using the PYTHON feedparser library - this library here is about RUBY.


Fix itensor rrule

This PR fixes a bug in the rrule for the itensor function, which now takes into account different index ordering. Before this fix, the gradients of these two functions were identical:
i = Index(2, "i")
j = Index(2, "j")
M = rand(2,2,2,2)

function f1(x)
  T = itensor(M, i',j',i,j)
  ...
end

function f2(x)
  T = itensor(M, i,j,i',j')
  ...
end

Looks good, thanks. I'll merge once tests finish running.

Codecov Report

Merging #773 (7d40768) into main (461d40d) will decrease coverage by 36.77%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##             main     #773       +/-   ##
===========================================
- Coverage   67.13%   30.35%   -36.78%
===========================================
  Files          92       91        -1
  Lines       10691    10426      -265
===========================================
- Hits         7177     3165     -4012
- Misses       3514     7261     +3747

Impacted Files
Coverage Δ

src/ITensorChainRules/ITensorChainRules.jl
0.00% <0.00%> (-71.76%)
:arrow_down:

src/physics/site_types/boson.jl
0.00% <0.00%> (-100.00%)
:arrow_down:

src/mps/observer.jl
7.14% <0.00%> (-81.23%)
:arrow_down:

src/physics/site_types/fermion.jl
0.00% <0.00%> (-80.65%)
:arrow_down:

src/mps/projmps.jl
0.00% <0.00%> (-79.07%)
:arrow_down:

src/iterativesolvers.jl
0.00% <0.00%> (-77.93%)
:arrow_down:

src/physics/site_types/qudit.jl
0.00% <0.00%> (-75.68%)
:arrow_down:

src/mps/diskprojmpo.jl
0.00% <0.00%> (-73.34%)
:arrow_down:

src/mps/mpo.jl
0.91% <0.00%> (-72.73%)
:arrow_down:

... and 69 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 461d40d...7d40768. Read the comment docs.

Thanks!


Option to emit ActionScript bytecode for Adobe AIR

Suggestion

🔍 Search Terms

ActionScript

✅ Viability Checklist

My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[ ] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion

Add option to emit ActionScript bytecode (aka. AVM2 bytecode or ABC) for writting Adobe AIR apps in TypeScript. Here's a document of AVM2: https://jmendeth.com/snapshot/4d9475cfb10af8142e331551dc9b91e1217dc8c6/media/2014-05-17-reverse-engineering-flash/avm2overview.pdf
ActionScript is a subset of EcmaScript 3 (ECMA-262 3rd edition), so it's doable. Plus, wherever possible, TypeScript can emit classes statically instead of prototype constructor functions when the extends clause resolves to a known class ahead of time.
📃 Motivating Example

The Adobe AIR framework is actively maintained by Harman: airsdk.harman.com. Apps are currently written either in ActionScript or Haxe by targetting ActionScript Bytecode (aka. ABC or AVM2 bytecode).
Adobe AIR is relevant for producing apps with unlimited data storage when compared to browser's indexedDB, localStorage and cookies. The flash.filesystem.File type supports URLs of scheme:

file: locates directory or file in the user's device
app: locates directory or file in the app's installation directory
app-storage: locates directory or file in the app's storage directory

This was just a brief reason for using Adobe AIR. There is also support for native extensions aka. ANEs, though I don't know how TypeScript can use them; should there be a way to say a function or method is native?
💻 Use Cases

You can develop data-unlimited apps with Adobe AIR compared to browser as stated above.

Same as #27362 and others. This is out of scope for TypeScript.

[x] This feature would agree with the rest of TypeScript's Design Goals.

You might want to read those again.

@fatcerberus I understand. I'd like to do it myself, but I don't know how to emit diagnostics and symbol tables and use them. I know there's an emit() method in Program at the compiler API, but it generates JS together.
Here's a discussion about that: https://github.com/airsdk/Adobe-Runtime-Support/discussions/2539#discussioncomment-5404173

Everything TypeScript has today supports this workflow - just not bytecode emit. --outFile with --module none is in reach. The only caveat is ES3 is now a deprecated target, so maybe you'd benefit from using ES5 while also linting against uses of keywords as property names (e.g. prefer foo["default"] over foo.default).


Tiny LineGraph improvements

LineGraph()(data, force_directed=True) forces the line graph
transform to treat the graph as being directed even if it isn't.
Also fleshed out pydoc for behavior in undirected case.

Codecov Report

Merging #184 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #184   +/-   ##
=======================================
  Coverage   99.65%   99.65%
=======================================
  Files          99       99
  Lines        2297     2297
=======================================
  Hits         2289     2289
  Misses          8        8

Impacted Files
Coverage Δ

torch_geometric/transforms/line_graph.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a633875...79522fe. Read the comment docs.


Problems with leap second?

Hi,
it seems I have problems with the time synchronization.
If I do a drive-google push there are thousands of files which are indicated as modified (Not all files in my drive). If I have a closer look at these files, they all have a time difference of exactly one second.
drive-google diff file.txt

local:            2015-03-24T20:58:8.000Z
remote:         2015-03-24T20:58:9.000Z

If I confirm the push command, there are no files uploaded (~2kiB/s) but the process takes a lot of time. At the end everything is in sync again.
Has anybody else observed this behavior?
PS: Because I was not able to update the drive version 0.1.9, I did a new installation.
drive-google version 0.2.5
go version 1.4.2
Kind regards,
Philipp

Hello again @philipp923! That is just a needed time synchronization needed as well as now there is a database instead of raw files being created in your <your_drive_mount_path>/.gd/indices. The indices need to be added to the DB so that's what took the bulk of that time. So you can get rid of the .gd/indices path

Hi odeke-em,
thanks for the very fast reply.
In this case I will execute the entire push and have some tea.
Regards,
Philipp

Cheers, enjoy that tea!


Enable some advanced rendering capabilities

In the ImageRendering class
o	Allow “color” parameter to take a list of colors
o	Add “classes” parameter, which defaults to None/Null (all classes) which allows only a certain number of classes to be rendered
o	Add “confidenceThreshold” parameter which will configure rendering only if confidence/“probability” is greater than the threshold value
o	 Add “regressionThreshold” dictionary, with keys for “filter” and “value,” where “filter” can be “gt,” “lt,” “gte,” “lte,” etc.
In the DocumentRendering class
o	Add “classes” parameter as defined above
o	Add “configdenceThreshold” parameter as defined above
o	Add “regressionThreshold” dictionary as defined above
In the WordRendering class
o	Allow “badge_color” to be altered as “color” parameter above
o	Add “classes” parameter as defined above
o	Add “confidenceThreshold” as defined above
o	Add “regressionThreshold” dictionary as defined above

Pushed to branch 0.2.0


Make --shell-isolation the default

For all the pipelines I have and try through gitlab-ci-local, I have to add the --shell-isolation option. I can't figure out a case where not having it would make sense? Why is it not the default?

https://github.com/firecow/gitlab-ci-local/discussions/335
Its in the next major...

Great!!


Supported extensions

Hi, i have a quick question.
Does model-viewer support these 3d models: (.3ds, .obj, .dff)?

No, we're glTF/GLB only.


[Toolkits] Allow overwrite of bracket when inserting functions from API toolkit

Autocompleting to a function uses the same code in CodeMirror that's normally used for inserting a bracket so you get a bracket pair. The closing bracket can be overwritten. Ideally we'd reuse this same code when performing API drops.
I suspect this will be hard and/or not worth it so I've split it out so we can discuss priority.

Historical note: the edits above are because the section now known as API was formerly called Reference (!)


[WIP] - Automatically launch DriveShare on login

DO NOT MERGE - WORK IN PROGRESS
This PR should add autostart behavior for Windows, OSX, and GNU/Linux systems.

This change adds an option to the Windows installer, but I think a better solution would be to have a Preferences Dialog in the app that allows users to modify this and other behaviors from within the application.

This looks good to me, you good to merge?


table 3

Dear author：
如何得到表3的结果呢，想学习一下

Hi, thanks for you interest in our work! The results in Table 3 are obtained by processing the videos frame by frame. Hope this can help you.


It should be possible to use different neural backends

Training data
Resources named mtl-en...
Config library

Example TorchScript Code
Branch supporting multiple backends

Start with NER because simplest
Run training in Scala and record performance numbers
Do in Python and compare performance


Credentials setup snippet doesn't work

Please notice, that in the "Credentials Setup" section for Linux there is a snippet for user's .npmrc, which is not working (at least, on my linux machine). All the uncommented lines should be prepended with double slash for it to work. See below:
; begin auth token
//pkgs.dev.azure.com/<yourOrganization>/_packaging/<yourFeed>/npm/registry/:username=[ANY_VALUE_BUT_NOT_AN_EMPTY_STRING]
//pkgs.dev.azure.com/<yourOrganization>/_packaging/<yourFeed>/npm/registry/:_password=[BASE64_ENCODED_PERSONAL_ACCESS_TOKEN]
//pkgs.dev.azure.com/<yourOrganization>/_packaging/<yourFeed>/npm/registry/:email=npm requires email to be set but doesn't use the value
//pkgs.dev.azure.com/<yourOrganization>/_packaging/<yourFeed>/npm/:username=[ANY_VALUE_BUT_NOT_AN_EMPTY_STRING]
//pkgs.dev.azure.com/<yourOrganization>/_packaging/<yourFeed>/npm/:_password=[BASE64_ENCODED_PERSONAL_ACCESS_TOKEN]
//pkgs.dev.azure.com/<yourOrganization>/_packaging/<yourFeed>/npm/:email=npm requires email to be set but doesn't use the value
; end auth token

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 96c25888-f381-be7f-2673-62621fe80da2
Version Independent ID: 3072da06-79cb-773a-f784-045babd04568
Content: Use npm to store JavaScript packages - Azure Artifacts
Content Source: docs/artifacts/get-started-npm.md
Product: devops
Technology: devops-artifacts
GitHub Login: @ramiMSFT
Microsoft Alias: rabououn

@aeldar Ok, thank you for your feedback!


Exception: finish pending transaction which is no longer in config

On startup, gdx-pay tries to finish pending transactions.
If this happens to be for a product that is no longer in the PurchaseManagerConfig.
Exception that occurs will be:
java.lang.NullPointerException
at com.badlogic.gdx.pay.ios.apple.PurchaseManageriOSApple.transaction(PurchaseManageriOSApple.java:222)
at com.badlogic.gdx.pay.ios.apple.PurchaseManageriOSApple$AppleTransactionObserver.updatedTransactions(PurchaseManageriOSApple.java:451)
at com.badlogic.gdx.pay.ios.apple.PurchaseManageriOSApple$AppleProductsDelegate.didReceiveResponse(PurchaseManageriOSApple.java:322)
at com.badlogic.gdx.pay.ios.apple.PurchaseManageriOSApple$AppleProductsDelegate.$cb$productsRequest$didReceiveResponse$(PurchaseManageriOSApple.java)
at org.robovm.apple.uikit.UIApplication.main(Native Method)
at org.robovm.apple.uikit.UIApplication.main(UIApplication.java:413)

Fixed in 0.10.1


Add support for rlsbb ddls

Can you please add DDL support to the scraper, debrid services can turn them into direct download links, just like torrents. Here is reference for the working scraper for a different app:
https://github.com/lalitjoshi06/Scrapers/blob/main/en_DebridOnly/rlsbb.json
Thank you!

can't even access the website.

can't even access the website.

Try any of these:
http://rlsbb.ru/
https://rlsbb.to/

If you still can't access any of those. Can you add support for this site? It's similar: psychodownloads.com


v2 col 2009-2021

Hi @gronert-m ,
As requested I updated the versions of COL for the variables occur_skills and veralt.
Best,
Alexandra

Thanks for this, @alexandraqn
Please delete the COL_V2 branch if it is OK with you.


python311Packages.hishel: 0.0.22 -> 0.0.24

Changelog: https://github.com/karpetrosyan/hishel/blob/0.0.24/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 288881 run on x86_64-linux 1

4 packages built:

python311Packages.githubkit
python311Packages.githubkit.dist
python311Packages.hishel
python311Packages.hishel.dist


Create Title Screen Scene

Create the title screen with final art, transitions between scenes and animated.
Create the buttons Game Start, Options and Exit.

[x] Title final art
[x] Buttons
[x] BackGround
[x] Transition
[x] Animation

EXPECTED RESULT:
A scene named TitleScreen.unity

Buttons added in commit https://github.com/RyuuSukeChan/ProjectDungeon/commit/9431619ec520e0b16f0c7d35231bad507afdd46a

Buttons animations added in commit https://github.com/RyuuSukeChan/ProjectDungeon/commit/80ef805d8bd957df9e6bda8c4d1d12a8337cce8b

Final Title art added in commit f39a9c081b40a74f8180807d749620ed08c66bde

Background and buttons art implemented in commit https://github.com/RyuuSukeChan/ProjectDungeon/commit/2d347e93423ec4e245965e31d3141f1f5fbd9b53


Can't execute a4apigen after installation

Hi everyone,
Background Info:

installed a4apigen
verified the directory in node_module to make sure it exist

Problem info:

can't run a4apigen; command used (with quotes, without quotes, etc):

a4apigen  -u "http://jelo-devd-webapp01.azurewebsites.net/swagger/v1/swagger.json" -o "./../../
../swagger"

error produced:

popup window.
Script: "...bin/a4apigen.js"
Line: 1
Char 1
Error Invalid character
Code: 800A03F6
Source: Microsoft JScript compilation error

3) My system info:

Angular 4.3.6
Typescript 2.3.3
OS is Windows 7
Angular cli 1.2.6
Angular comiler-cli 4.3.6
node v8.2.1
npm v5.3.0

Install it globally.


(vim) AV detections

Chocolatey Version
1.3.0
Chocolatey License
None
Package Version
All
Current Behaviour
Packages are being held for moderation and will be rejected as there are too many AV detections with no description notes as to why.
Expected Behaviour
A note in the descrtption confirms why the AV detections are high.
Steps To Reproduce
N/A
Environment
N/A

Chocolatey Log
N/A

Anything else?
No response

PR #2148 merged.


Enable Telemetry during Scale Test

As a user of NGF that leaves telemetry enabled
I want NGF's release tests to be run with telemetry enabled
So that any extra overhead is accounted for in the results of the test.
Acceptance

Telemetry is enabled during the scale test
Telemetry data is not sent to the Data Fabric production environment.

Dev Notes

will require a custom image with oss dev endpoint
NGF installation in test needs to be updated to not disable telemetry
GKE cluster in NFR tests needs a router (make create-gke-router) to allow NGF to send anything over the internet

Team has determined there is nothing of significant value to test with this.


Sandbox should not load from NetCrs

Currently, since there's no CRS file readily available, we fallback to NetCrs. This currently isn't too big a download, but as we saw with a dodgy network setup, it can fail, and we will eventually want more points. We should download as many points as we need ahead of time.

Yep, we will sort this.

For this, can we identify the points needed from the CRS, put them into a file/s and ship that file with the sandbox image and the cli npm package. This way, once they have been downloaded and installed the user can effectively work offline.

That was what I was thinking. Essentially take the current range headers, use that to curl download a portion of the transcript, ship that at a path that can be found, and if they need more then we instruct the user on how to download the full file (or for now perhaps just say instructions to come, please tell Aztec you need this)


[UPDATE] New skins

snakebite collection i guess

New collection or not, Osiris already has the skins available because it finds the textures in the pak01_dir.vpk :)

New collection or not, Osiris already has the skins available because it finds the textures in the pak01_dir.vpk :)

and new update breaks osiris afaik, one of my friends mentioned it


Verify links in webapp against VuePress sitemap

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1284
Originally created by @bencodezen on 2019-11-08 16:21:44

Problem
Links in the webapp can become outdated, so we need a way to automatically verify that the links actually go to the proper site on meltano.com.
Solution
Fetch links in project and verify against sitemap

View 4 previous comments from the original issue on GitLab


minor: Remove unnecessary logic

Which issue does this PR close?

Closes #.
Rationale for this change

This removes some unnecessary logic in QueryPlanSerde when handling Final aggregation mode.
What changes are included in this PR?

After #155, some previous logic on handling Final aggregation mode is no longer needed.
How are these changes tested?

Existing tests.

Codecov Report
Attention: Patch coverage is 50.00000% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 33.25%. Comparing base (56ccf6a) to head (2585f46).

Files
Patch %
Lines

.../scala/org/apache/comet/serde/QueryPlanSerde.scala
50.00%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #169      +/-   ##
============================================
- Coverage     33.27%   33.25%   -0.03%
  Complexity      763      763
============================================
  Files           105      105
  Lines         35371    35353      -18
  Branches       7663     7657       -6
============================================
- Hits          11770    11756      -14
  Misses        21151    21151
+ Partials       2450     2446       -4

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Thanks, merged


Set the IP address of the outgoing test request

Hi, is there any way to set the IP address of the mock request? I have a use case where I need to know the IP address of the incoming request. The library sets the IP address to an empty string. I need to set it to a particular value (could default to <IP_ADDRESS>). Any help would be much appreciated.
Thanks

I've been doing this by setting a fake server address directly after creating the engine:
e := NewEngine()
e.Server.Addr = FakeServerAddress

but this must be matched on the server side with something like:
// get the IP address of the running server
func GetServerAddress(c echo.Context) string {
	serverAddress := c.Request().Host
	if serverAddress == "" {
		// normally we use the address given in the HTTP request
		// this is not set by gofight in unit tests so we use the listener address instead
		if c.Echo().Server != nil {
			serverAddress = c.Echo().Server.Addr
		} else if c.Echo().Listener != nil {
			serverAddress = c.Echo().Listener.Addr().String()
		}
	}
	return serverAddress
}

Rather than using c.Request().Host directly as this could be a different IP, for example if your server is running inside a docker container.


provide for automatic rollback

Codecov Report

Merging #27 (66bfccc) into master (fbc9ca1) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #27   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            4         4
  Lines          466       466
=========================================
  Hits           466       466

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fbc9ca1...66bfccc. Read the comment docs.


saveSvgAsPng.js:222 Uncaught TypeError: Cannot set property 'prepareSvg' of undefined

I have downloaded the project and built a es2015 js file and included it with a script tag to my page.
When I load the page, following error is shown in the console:
saveSvgAsPng.js:222 Uncaught TypeError: Cannot set property 'prepareSvg' of undefined
And when I try to use the function saveSvgAsPng(), I get a ReferenceError:
Uncaught ReferenceError: saveSvgAsPng is not defined
Here is the code of my usage:
function exportToPNG() {   saveSvgAsPng(document.getElementsByTagName("svg")[0], "diagram.png"); }

I had to add an array accessor "[0]" to the svg object in line 37, 39, 48, 49, 91 and 92 to get it work. But now I only get a black rectangle.

Based on the error messages you report, I'd say the following line is returning undefined for some reason:
https://github.com/exupero/saveSvgAsPng/blob/ff408c983b27091f3de2b6fa05bac214df58266f/src/saveSvgAsPng.js#L2
That seems very unusual. this should be window if the library is included as a script tag.
Also, I don't understand the line numbers you gave. What file? They don't seem to have any relevance to your comment in the main script file.

I'm seeing the same thing -- because this is actually undefined, not a reference to the window object as expected...
FWIW, the way I'm including your library is by appending this element:
<script src="vendor/save-svg-as-png/lib/saveSvgAsPng.js"></script>

at the end of my html page, inside the <body>...</body> tags. So the file is local to the same web server, and the file contents are properly being returned with the correct content-type. Hope this helps.

Florian,
Until this is sorted out, you can modify the second line to include  || window; at the end -- since that is what this is supposed to point to anyway...


Support non-repeated non-map page streaming resources

Specifically adds support for the genomics.references.bases.list
method, which returns a page streaming response where the page streaming
resource is a string.

This PR I think will have to be reviewed offline...
I added the genomics baseline to test the non-repeated non-map resource - the only method worth looking at is the one in the commit message.
Search for ListBases in the baselines or 'sequence' and you'll find it.

Current coverage is 81.45% (diff: 91.66%)

Merging #853 into master will decrease coverage by 0.69%

@@             master       #853   diff @@
==========================================
  Files           323        323
  Lines         12410       9538   -2872
  Methods           0          0
  Messages          0          0
  Branches       1612       1550     -62
==========================================
- Hits          10195       7769   -2426
+ Misses         1787       1352    -435
+ Partials        428        417     -11

Powered by Codecov. Last update 88c1975...61aefb6

Okay, compilecheck passes in all languages

Something seems a bit weird with the Java baselines on Github, and I'm not seeing the blank lines show up. Does it look right to you?

You're right, something or another happened - I think it's fixed now, good call

No... github still isn't showing the Java diff properly...

Ok it's fixed now

Gonna claim that we're good to go, if you happen to see an issue at any point I'll fix it up.


mark link header discovery as at risk

As discussed in https://github.com/solid/webid-oidc-spec/issues/18#issuecomment-486453876

👍

+1

I understood that @kjetilk currently acts as editor in all spec and merges PRs

Yeah, at least we're trying to draw up a process around it so that we can get things done :-)

@kjetilk I think we have agreement on this one, can you merge this?

I don't have access to merge this.

@kjetilk can you merge this?

Ah, right. We haven't got the labels that we use in solid-spec here, but I think it has had sufficient review time.


[WIP][Bug] Direct Dictionary Complex primitive timestamp type support in data loading and query

retest this please

LGTM


Tell Cypress to retry twice if an e2e test failure occurs

Description
This PR is an attempt to try to "stabilize" a few e2e tests which are semi-flakey right now.  The flakey tests seem to all relate to searching. If the test search doesn't respond in 4 seconds, the test times out.  It seems like the test backend (which is being searched against) might be responding slowly at times (or maybe getting bogged down temporarily?).
In any case, it only seems to happen randomly so far, and in the same e2e test run, usually some of the search tests succeed even while one fails.  This implies to me that we are hitting some sort of temporary slowness in the search response.
So, for now, I'm just adding a configuration for Cypress to tell it to retry twice if a test fails. This means it'll run a maximum of 3 times before an error occurs.
I will see how this PR behaves in our CI environment to see if it at least makes e2e tests less likely to randomly/temporarily fail.

This PR works.  In the 14.x build of this PR, one of the search-navbar.spec.ts tests even triggered a re-try (failed first time & succeeded the second): https://github.com/DSpace/dspace-angular/runs/4564137363?check_suite_focus=true#step:13:993  So, this appears to give us more immediate stability.
Therefore, I'm merging this immediately so that it can help others seeing random failures in the search e2e tests.


Hot Corners

Description of the new feature / enhancement
Just like the MacOS, hot corners would execute a selected command (sleep, screen off etc.)
Scenario when this would be used?
an example scenario would be ; if you'd like to turn the screen off, you'd drag the mouse pointer to the selected corner and the screen would turn off.
Supporting information
MacOS Settings have hot corners. There's also a win app called WinXCorners, but would rather have this in Powertoys

/dup #1305


Toggle for remembering subtitle tracks and remember all tracks instead of only the first.

Subtitle track selector remembers all three tracks instead of just one.
Added toggle for remembering subtitle tracks.
By default, the toggle is checked when all preferred tracks were auto-selected. It defaults to unchecked if one or more preferred languages were not available. This prevents preferences from being overwritten with empty in instances where the preferred languages were not available whilst still giving the user the option to overwrite them if they want to.

Thanks!!


Custom x and y accessors

We've been kind of assuming people will use x and y as the names of their respective data names, which is pretty inflexible.  We should probably let them specify a custom x and y accessor.  So, they could do something like:
<Chart x_accessor="event_dates" y_accessor="event_values" />
And then instead of using point.x and point.y, we'd use point.[props.x_accessor] etc.
Does this sound reasonable?

Yeah this sounds true. Same thing for label and value too ?

Done for x and y accessors.  I'm still thinking about label and value accessors.


inject Stager In Terminal And Control inject Via Github //  All Of Systems Linux/Mac

You can see it On This Video And if you want to integrate it Normal ! !
The will i provide the files //
https://www.youtube.com/watch?v=Y9no9xbsmTA&t=25s

@ThePirateWhoSmellsOfSunflowers

?


Add reusable way for users to fill in JSON objects

'create' calls should be done in a way that ensures the least possible repeated code. It should also ideally be easy for a MOPS CLI user to figure out what each object looks like.

Closed by 3ca22a692da6b6b487b4c9ce1e39c4a9e17b26f8.


RHEL/CentOS 7 requires rpcbind service before nfs

When calling include_recipe "nfs::server" on RHEL/CentOS 7, it is generating the following error
       Recipe: nfs::server
        (up to date)

           ================================================================================
           Error executing action `start` on resource 'service[nfs-server]'
           ================================================================================

           Mixlib::ShellOut::ShellCommandFailed
           ------------------------------------
           Expected process to exit with [0], but received '1'
           ---- Begin output of /bin/systemctl start nfs-server ----
           STDOUT:
           STDERR: Job for nfs-server.service failed. See 'systemctl status nfs-server.service' and 'journalctl -xn' for details.
           ---- End output of /bin/systemctl start nfs-server ----
           Ran /bin/systemctl start nfs-server returned 1

           Resource Declaration:
           ---------------------
           # In /tmp/kitchen/cache/cookbooks/nfs/recipes/server.rb

            47: service node['nfs']['service']['server'] do
            48:   action [:start, :enable]
            49:   supports status: true
            50: end

           Compiled Resource:
           ------------------
           # Declared in /tmp/kitchen/cache/cookbooks/nfs/recipes/server.rb:47:in `from_file'

           service("nfs-server") do
             action [:start, :enable]
             supports {:status=>true}
             retries 0
             retry_delay 2
             default_guard_interpreter :default
             service_name "nfs-server"
             pattern "nfs-server"
             declared_type :service
             cookbook_name "nfs"
             recipe_name "server"
           end

       Running handlers:
       [2015-11-17T23:50:53+00:00] ERROR: Running exception handlers
       Running handlers complete
       [2015-11-17T23:50:53+00:00] ERROR: Exception handlers complete
       Chef Client failed. 4 resources updated in 10.300837409 seconds
       [2015-11-17T23:50:53+00:00] FATAL: Stacktrace dumped to /tmp/kitchen/cache/chef-stacktrace.out
       [2015-11-17T23:50:53+00:00] ERROR: service[nfs-server] (nfs::server line 47) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
       ---- Begin output of /bin/systemctl start nfs-server ----
       STDOUT:
       STDERR: Job for nfs-server.service failed. See 'systemctl status nfs-server.service' and 'journalctl -xn' for details.
       ---- End output of /bin/systemctl start nfs-server ----
       Ran /bin/systemctl start nfs-server returned 1
       [2015-11-17T23:50:55+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

Looking at https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Storage_Administration_Guide/s1-nfs-start.html, the rpcbind service should be started before the nfs service.
To resolve, I had to add the following to my cookbook:
include_recipe "nfs"
if node['platform_family'] == 'rhel' && node['platform_version'].to_f >= 7.0 && node['platform'] != 'amazon'
  service "rpcbind" do
    action [:start, :enable]
    supports status: true
  end
end
include_recipe "nfs::server"

Does this continue to work on restart? We ran into a similar issue (see https://github.com/atomic-penguin/cookbook-nfs/issues/52#issuecomment-123842200) and had to update the systemd dependencies for nfs-target to start rpcbind on boot because it was installed as a static service and could not be individually enabled.

What do you mean by restart? service restart or OS restart?
Following the Red Hat documentation, rpcbind is required. Not sure we should modify systemd when all that needs to happen is start it first.

System restart. We were hitting issues with NFS clients not mounting on boot with long waits for a timeout somewhere. The solution was to put rpcbind.service into the requirements for nfs.target (I think those were the right unit files, I'm doing this from memory right now). There's a method of augmenting systems unit files without changing the distribution-provided files.

I believe it does work on system boot.
According to
https://docs.chef.io/resource_service.html
The service :enable action will launch the service on boot.
Anyway, I can confirm that this works for me too.
So I'll raise a PR to include this in the cookbook.


port to ts

Move the code base to typescript. Just a refactor, nothing should break but imports from require(feathers-hooks-common/lib/...) or require(feathers-hooks-common/types)
We should make it a major version, just to be sure.
What do you think @daffl ?
Issues: closes #656
PRs: closes #662, #646, #634

Amazing! I wonder how many things for this would break/change with the latest v5. It does have a good chunk of TypeScript related changes - especially around the hook context.

We can totally merge this one first once you put it into the ready for review state.

It's ready 😊

continuing on #663


Auto inserted settings have validation warnings

Testing #205384

Enable all announcements

Enable all audio cues

:bug: auto-inserted settings get validation warnings:
"accessibility.signals.chatResponseReceived": {
    "sound": "on",
    "announcement": "off"
},


Adds a snippet insertion destination

This is especially useful when you are writing code

Very cool idea. How well does it work in practice?
I'm not sure the fact of it being a snippet is a destination; seems somewhat orthogonal but I'm not sure I have a much better idea and this stuff is still all quite experimental so probably ok

It seemed to work pretty well when I was testing last night. I'm going to keep trying it out and see how it goes. I'm excited at the possibility it provides for the LLM to clearly point out the parts of the response that should be adjusted, which is a pretty useful way to communicate.

I agree about it being somewhat orthogonal to insertion method-it's more of an adverb that could be applied to above/below/replace. We don't have that in the grammar yet though.

Interesting idea. I feel like this could significantly benefit from multishot prompting. Since I feel like the model could interpret the prompt as it is now in many different ways. But multishot prompting is probably a story for another PR.
If you are finding this to be practical, I think we should create a new talon list called modelInsertionModifier or something similar. We can then also include selected in that list if you want to always paste with text selected. I would prefer to pass in modelInsertionModifier instead of modelDestination just to make it very clear that snippet is not a destination, but a way by which the text is inserted differently.
But I'd experiment with things a bit before making too many changes.

And once again my only hesitancy with this is that is does seem very experimental and I am not really sure if the added complexity to the grammar is worth it. I think most people would want to just say the snippet in community they want. Arbitrary text instructions usually doesn't conform to snippets as well compared to well defined blocks (classes, if statements, specific boilerplate etc)
As with everything this does have a use, I suppose we just have to see how useful since I haven't played around with this myself.

insertionModifier sounds good to me

To make things consistent with the other code in this repo, I made a couple quick edits and opened a new PR #85 , let's discuss further there. I actually think that snip should be a prompt with arbitrary text after it like ask so I made some refactors.

I made another alternative inspired by #85 : https://github.com/C-Loftus/talon-ai-tools/pull/86

Closing in favor of #89


add support for heterogeneous insert

This pull request adds support for heterogeneous. This is useful for the same reasons as heterogeneous lookup. You can for example insert words from a string into a set of strings, without unnecessary memory allocations (see example).
In addition to the requirements for heterogeneous lookup the "key" type has to be constructible from the "key_equal" type.
I strongly recommend using an explicit constructor otherwise you always live in danger of silent copys.
The changes required for this to work are very minor, because most of the code is already generic.
Right now it's only implemented for robin_set and not tested throughoutly, because i want to know what you think about it before i waste my time.
example.cpp.txt

Hi,
Thank you for your contribution.
Currently you're implementing the insert with the heterogeneous key only for robin_set, how do you plan to do it for robin_map? The current insert method of the map takes a std::pair<Key, T>, would you create a similar method to accept a heterogeneous key in the first element of the pair and then create a real std::pair<Key, T> if needed? Or do you plan to change try_emplace to accept a heterogeneous key (but then we will have a weird mismatch between the API of the set and the map where one accept heterogeneous keys for the insert method but the other only for the try_emplace method).

Because i had a real use-case for the set, i didn't think about the map honestly. Let's say we want to modify my previous example and count the number of distinct words. This would work perfectly fine with your first suggestion (create real pair if needed).
One could object that this is not optimal, because when we create pair<Key, T> from pair<KeyEqual, T> we have to move/copy T, which might be expensive. For this map it is not an issue, because it's using open addressing. If moving T is expensive you have a much bigger problem anyway, because T might get moved on rehash (even insertion of other elements in case of robin hash).
Only in case a consistent API with other maps is needed, one might think about passing KeyEqual and T as separate arguments (with & and && overloads). I think this is a bit too speculative and could still be added later if necessary.
I'll implement insert taking a std::pair<KeyEqual, T> when i find some time in the next days...

Closing, as out-of-date. Don't hesitate to reopen if it's a feature that is still needed.