-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crashlytics not be logged on iOS platform #57
Comments
Is it only happening for ad-hoc builds? |
Had no crashlytics for any builds we've tried on iOS. AdHoc was used to test on a production build. |
If you only used adhoc for the production builds, I know whats the issue. It's that we only check for "production" here |
Not sure I understand, an AdHoc build is a production build. Only difference is that it is signed to work on registered devices. This shouldn't affect the underlying code or how it behaves. |
We have a CLI hook that checks different deploy types, so I was wondering if it may be skipping a dist-adhoc vs dist-appstore build. But if you don't see the log |
Could it be an issue with Alloy based apps? I created a fresh Alloy app with only the Firebase modules and crashlytic modules included, following the setup instructions here and still got nothing coming through. |
We use Alloy as well, so it should be fine. Did you review the README to have the correct structure? |
Yes, app is setup exactly as instructed in the README. |
Got the same issue with latest version on classic app -- no errors reported in app or log entries for CA and nothing sent through to firebase -- this is on simulator. |
Same issue as reported in #50 which had been closed. Re-opening as this still doesn't work on iOS with the latest version v4.4.0. See my comment #50 (comment)
This has been tested with an AdHoc build of the application running on an iPhone 11 device forcing a crash to occur whilst the app is running. No crash logs have yet been recieved on the Firebase Crashlytics dasboard.
Titanium setup:
The text was updated successfully, but these errors were encountered: