I have implemented Firebase/Crashlytics to an app. I can see in the logs that app is sending crashes. Firebase Console doesn't show anything. I can see crash free user count decreased after the implementation. Console doesn't show up anything. Please help. My app ID: com.obssmobile.mychesspuzzlegame
I have disconnected the Xcode debugger, relaunched the app and remade the crashes. Issue is persisting.
Here I can see that crash free users started dropping.
Here I can see "report submission successful" log
Console is not updated after several hours.
For apps migrated from Fabric that have been deleted and reintegrated with Firebase, sometimes a linking issue in the backend can cause your app to go into a state where the Firebase listener is unable to make the correct settings request to onboard your app using the new SDK. In these situations there are currently two workarounds.
Delete your app, and reonboard with either a new bundle ID or using the same bundle ID in a different Firebase Project.
Write in to Firebase support and they can try to manually delete the backend link that's causing this issue. However, this should only be done if you have a lot of historical crash data that you need to preserve.
Related
happy to see you again.
I was successfully submit and update application in appstore.
here iam facing one issue while updating app from app store app is getting crash(after launch Screen).
while on fresh installation application is working good.
no crash while testing and in TestFlight.
no crash reports available from store.
here I am using firebase db.
finally it's important to inform you.
my db is different from previous version(fbdb_1) to present version(fbdb_2).
whole data is same for two db's.
Any suggestion would be helpful in my learning journey
Checking for unsaved keys in home screen, due to this app is crashing.
Updated keys and now working fine without crash.
Please guide me! Why Firebase console take much time to communicate with server. I'm waiting one and half hour to complete this takes. Anybody tell me what is the reason behind this issue or anyone facing this issue before.
Not show the Graph.
Please make your app force fully crash 2-3 times, after disconnecting your app from Xcode.
This is what worked for me.
In my case, I solved this problem by doing these steps:
Make sure you follows the all steps that mentioned in Firebase Documentation Crashlytics.
Use fatalError() for crash your app.
Uninstall App from simulator or Real Device
Run the app on Simulator or Real device then stop running.
And then Open the App that Install on Simulator or Real device.
Open Firebase Console project And Refresh it.
This can happen as a result of several different issues, however they're usually connected to your app being unable to make the proper call to the Crashlytics settings endpoint. You can either write in to Firebase support, or feel free to start a private thread with me, and I can check your apps settings in the Firebase backend.
if you followed all steps as per latest crashlytics documents!
try forcing a crash directly with button click on initial view instead of just building and running your app
use fatalError() for crash your app
I'm developing an app and am ready to release it to a small group (5) of testers for internal testing, so I added their Gmail addresses to the list:
I sent one of the testers the link to the app and after opening email and selecting the link, they got this:
followed by this:
So far, so good. Now when I select the tester in question, instead of advancing to the next page, which is the start of a tutorial (as the app does when it's run from Android Studio), it returns to the previous screen. No error message or crash (I checked with Crashlytics). Anyone have any idea why this is happening?
UPDATE: I added Firebase event logging to my app and saw that no events are being logged from the LoginActivity (on the other hand, when I install the app via Android Studio, events DO get logged). Logcat shows a NameNotFoundException thrown by the PackageManager for for the app's package. Thinking the package manager doesn't like app bundles, I generated an APK instead, but got the same problem.
UPDATE #2: The next thing I tried was re-installing the app via Android Studio. When I simply let the app run, it exhibited the same problem, but if I ran it in Debug mode, it was fine. Not a solution, just a clue.
If I don't get this resolved by this weekend, I'll have to email my testers the APK. I wish someone in the Firebase group were monitoring this problem because emailing APKs as a workaround really sucks!
UPDATE #3: Getting closer to the cause of the problem. The reason that events weren't getting logged in LoginActivity was because I was using a reserved event name: user event names cannot start with "google". After fixing that, events did start getting logged, including an ApiException "10:" when trying to log into a Google account. So I googled around and I THINK the bottom line is that when I opted into Google App Signing I may have uploaded the wrong app signing key. If that's the case, how do I upload the correct one? I hope the answer isn't "create a new app with a different package name and start over".
After opting in to App Signing, I neglected to copy the SHA-1 fingerprint into my Firebase settings. Also, I needed to rebuild the app with the updated google-services.json. After doing all that and updating the release, the opt-in link worked fine.
I got email from fabric that my iOS app has issue and dropping crash free users but when I am testing, app is working fine without any error or crash even I checked twice XCode logs too.
Here the screenshot:
User's question was resolved by support(at)fabric(dot)io. The filter was pre-cached for a previous date which had no crashes. Resetting the filter populated the correct data.
I have a serious issue which I cannot seem to solve.
Recently I have made an update to an IOS app, and when testing in XCODE as both Ad-Hoc, Debug, and installing via the .IPA on a device the issue cannot be replicated. However when I download the app from the App Store, it crashes.
Does anyone know how this could happen, and any potential solutions? I am getting lots of complaints from users, and not sure what to do?
Could part of the binary upload have got corrupted?
Probably you always compiled your app in debug mode. But when sent to App Store you made a release compile. click the arrow in the run button select scheme and chose "release mode" and run your app it will probably crash.
check if you used NSParameterAssert as they are not called in release mode
I cannot say why your live App Store application is crashing and the debug version is not. Two possible solutions:
Crash reports:
To find out why your application crashed, you might want to check if there are any crash reports available on iTunes Connect. Log in on iTunes Connect and click on your application. Scroll down to Crash Reports. You will find out more about why your application is crashing here.
More information about crash reports here at Apple's own iOS Developer Library.
Prerelease your app with TestFlight: For in the future: test your application by uploading it on iTunes Connect and testing it with TestFlight first before submitting the application to the iTunes Store. This will save you a lot of (review) time if you find a error.
I realize this is an old thread but I had the same issue with my App that I released. Meaning it worked fine in testing, but when I released it it would crash. The culprit ended up being the fact that I am using In App Purchases. I have two items that can be "bought" but I had only enabled one of them. In testing it was able to read both of them, but with the release version, it was only pulling the one that was enabled down, creating the crash. The fix was simply enabling the disabled item. I didn't even have to redistribute the app, though I had to wait for it to "percolate" through... Anyway this may help someone in the future.
Check if your app is looking for too many IAPs.
I just had this problem and my problem was I had deleted an IAP from the App Store, but didn't remove it from the app code.
For some reason it only crashed when downloaded; I used a promo code to do this before launching my app.
Thanks to Tornado for the inspiration to try this variation.