-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Crashlytics in tvOS for Apps without Fabric App #3511
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
Comments
This comment has been minimized.
This comment has been minimized.
Tracked internally at b/139003562 |
At this time you can still create new apps in the Fabric console. This is the recommended path. I have let the team know . :) |
Do you mean the dashboard in https://fabric.io/settings/apps ? beacause if I click the add button it redirects me to the home page https://fabric.io/kits |
Hey @bjimenezned, it sounds like you got the setup right. I took a look at this and think there is an issue in the backend. I'm gonna work on getting this fixed and then update this bug. |
Hey @bjimenezned, can you try onboarding your app in Firebase again? The issue should be resolved now. For future tv and macOS onboarders, my recommendation is to follow the onboarding steps for an iOS app, and include the following in your Podfile if you want Crashlytics:
|
Seems to be working now, I managed to link and receive crash reports in firebase console. Thanks! |
Uh oh!
There was an error while loading. Please reload this page.
Is there a way to use Crashlytics in a new tvOS app. Since now you can't create a new Fabric app, #2009 solution is not possible anymore.
I tried integrating it as a new iOS App but test crashes are not showing up in the console (yes, I did read/follow the Firebase Crashlytic integration instructions for new apps step by step, and the firebase integration is working since I can use FirebaseDatabase without issues)
Most issues in here seems to apply to older apps with a Fabric app already created, but how does it work for a new Firebase tvOS App?
The text was updated successfully, but these errors were encountered: