Skip to content
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

Open
ASankey-Ideagen opened this issue Jul 7, 2022 · 9 comments
Open

Crashlytics not be logged on iOS platform #57

ASankey-Ideagen opened this issue Jul 7, 2022 · 9 comments

Comments

@ASankey-Ideagen
Copy link

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:

Ti SDK:               10.1.1.GA
Alloy:                2.0.1
iOS:                  15.5 - iPhone 11 device
Xcode:                13.4.1
Firebasecore:         7.2.0 
FirebaseAnalytics:    6.2.0
FirebaseCrashlytics:  4.4.0
@hansemannn
Copy link
Owner

Is it only happening for ad-hoc builds?

@ASankey-Ideagen
Copy link
Author

Had no crashlytics for any builds we've tried on iOS. AdHoc was used to test on a production build.

@hansemannn
Copy link
Owner

hansemannn commented Jul 7, 2022

If you only used adhoc for the production builds, I know whats the issue. It's that we only check for "production" here

@ASankey-Ideagen
Copy link
Author

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.

@hansemannn
Copy link
Owner

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 Skipping Crashlytics injection for non-production build …', it must be something else, though I am sure it's something in your setup, because most of the people use it without issues.

@ASankey-Ideagen
Copy link
Author

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.

@hansemannn
Copy link
Owner

We use Alloy as well, so it should be fine. Did you review the README to have the correct structure?

@ASankey-Ideagen
Copy link
Author

Yes, app is setup exactly as instructed in the README.

@jasonkneen
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants