For my app, I tried to configure the Firebase Crashlytics. For configuring I’m not using the pod file. Installed Firebase Without Using CocoaPods. For that I followed the following link:
https://mokacoding.com/blog/setting-up-firebase-without-cocoapods/
Then I added GoogleService-Info.plist to the project from the Firebase account.
After that, I changed the DEBUG_INFORMATION_FORMAT from DWARF to dwarf-with-dsym in Build options. Then I added the Run script in the Build phase.
Added the following script:
"${PROJECT_DIR}/ProjectName/GoogleService-Info.plist" -p ios "${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}"
For install build only selected
Based on the dependency analysis is selected
Then in input files, I added the following:
${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}/Contents/Resources/DWARF/${TARGET_NAME}
$(SRCROOT)/$(BUILT_PRODUCTS_DIR)/$(INFOPLIST_PATH)
Changed the Scheme from debug to release.
I could not able to get the crash from crashlytics console. Is any issue is with the run scrips?
I appreciate your help in advance.
These configurations are not directly related to Crashlytics' crash report operation. These are used to send desymbollers to Firebase. So Firebase can desymbol your crash info and provide you a readable crash report. So, I am not sure that a failure in these configurations can cause your problem. As I know, if you have a failure in these steps; After your app crash, you need to see "Missing dsymbols" error on Firebase Crashlytics panel
If you cannot see your crash report, you need to check steps to integrate crashlytics properly. And maybe enable Firebase debug mode and check logs.
By the way, Crashlytics' first integration steps may be annoying. You may need to read and apply these steps carefully. Especially test crash step.
Related
My flutter app works fine on debug and profile builds but crashes on release build. I would like to understand why it crashes on release build. Is there any way to see exceptions like I can see in debug mode? It is not enough to see print logs which I can see print logs and does not help. I need to know where and why the app crashes. So it would be helpful if I can see exception logs. I suspect insufficient pro guard rules causes this problem but I don't know which rules should I add more. If I can see exception log, this would help me to add correct rules to pro guard.
Connect your physical device or use any emulator and then run your app using this command flutter run --release from the terminal. You'd be able to view the logs in the release mode
I suggest to use third party tool to track production exceptions. I recommend Sentry (I am not employee, just happy user) as it is easy to configure and works out of the box.
Check https://pub.dev/packages/sentry package and https://sentry.io/ for documentation.
Please note that Sentry works ONLY at production. Also note that if your app crashes, the error is logged next time you try to open the app, and not immediately after the crash.
When deploying a flutter application on Google Play Store the following warning message appears:
Warning
This App Bundle contains native code, and you haven't imported any debugging symbols. We recommend importing a symbol file to help analyze and debug crashes and ANR errors.
That is something coming from the Flutter codebase itself. Its been like that for a long time now and hope the future releases resolve that.
For now, you can simply ignore the warning and proceed with publishing the app.
We tried to use speech recognition package - https://pub.dev/packages/speech_recognition in our flutter application along with other packages. The app was built successfully and installed, but we could see only a white screen on the iOS device. There was no error log that could tell us that this package created a problem. Once this module was removed we were able to see the application on the phone. This was done by manually checking for each package. I wanted to know if there is any runtime error handling methodology that could be used to log runtime errors and generate a logfile.
We are still researching on this issue, so we havent executed anything. Any suggestions would be welcome.
I building an XAF Winforms App located here following this blog
I am having a difficult time getting my Desktop Bridge application to pass the
Windows App Certification Kit tests
The report states that the App Resources tests fail.
Error Found: The app resources validation test detected the following errors:
The test was blocked from execution. Please try re-running the validation. If the test execution remains blocked then please contact support.
Impact if not fixed: The app might not install if the strings or images declared in your app’s manifest are incorrect. If the app does install with these errors, your app’s logo or other images used by your app might not display correctly.
How to fix: Fix the problem indicated by the error message. See the link below for more information:
App Package Resource Validation
The report also has errors in the Package Sanity Test
Blocked executables
Error Found: The blocked executables test has detected the following errors:File SBD.GL.Win10\DevExpress.XtraReports.v18.2.Extensions.dll contains a reference to a "Launch Process" related API System.Diagnostics.Process.Start
I have tried re-generating the image files and looking through Package.appxmanifest
The help that the error message links to does not contain the error text to look up.
[Update]
I think the issue is related to Nuget installing packages that
I am asking about this at Dev Express
As described in the DevExpress forum, this looks like a false positive from WACK tests. I would recommend to proceed with the submission.
i integrated crashlytics into my unity game, everything worked fine, but then i had to change my package name and my working mail, since then whenever i open the dashboard it gives me an alert "Sorry the app could not be located".
I reinstalled the crashlytics sdk in unity, used new login in prepare fabric tab, but the issue is still there, although the crashlytics seems to be working.
Thanks. Usually this means we aren't detecting the build and run event. Please make sure you are building and running in the relevant IDE. Also, clean your app and dependencies in the native IDE to make sure the bundle ID is updated in all locartions. If you still run into issues, you will need to contact support as your app may be in a weird state in our system.