search

hansemannn / titanium-crashlytics

Use the native Crashlytics SDK in Titanium (iOS / Android).
MIT License
18 stars 18 forks source link

Crashlytics not be logged on iOS platform #57

Open ASankey-Ideagen opened 2 years ago

ASankey-Ideagen commented 2 years ago

Same issue as reported in https://github.com/hansemannn/titanium-crashlytics/issues/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 https://github.com/hansemannn/titanium-crashlytics/issues/50#issuecomment-1168502886

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 commented 2 years ago

Is it only happening for ad-hoc builds?

ASankey-Ideagen commented 2 years ago

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

hansemannn commented 2 years ago

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 commented 2 years ago

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 commented 2 years ago

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 commented 2 years ago

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 commented 2 years ago

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

ASankey-Ideagen commented 2 years ago

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

jasonkneen commented 1 year ago

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.