Before now in Fabric Beta
I could add new testers via Add Testers button:
How could I add new testers via Firebase platform?
firebaser here
Fabric/Crashlytics Beta is not yet available under the Firebase umbrella. We're working on it, and it will be available later this year under the name App Distribution.
I recommend taking a look at the Fabric roadmap, which also contains a link to request early access to Firebase App Distribution.
Just in case anyone finds this question. When you go to Firebase console:
Select the project you want to manage
Go to App Distribution on the menu on the left side. (the main view should display App Distribution title)
Select 'Testers & Groups'
Related
Probably silly question, but is it possible to send errors using Crashlytics from users that downloaded my app from Google Play? Until now I was using Crashlytics to collect errors from my app distributed by Firebase (so it was only for me and invited people). But I have released my app on Google Play and I can't see any errors from devices that downloaded my app in Google Play. I read that when I link my Google app with Firebase I can see purchase and subscription and analytics but no mention of Crashlytics. So my question is.. Is it even possible? Thank you very much.
Is the package name the same on your "release" version on the store? If your test one was called com.patrik.coolapp.debug (which is the default if you're using a debug build) then you'll need to add com.patrik.coolapp as an App in your Project in the Firebase console.
If you already had Crashlytics set up (all the dependencies, added the plugin, FirebaseCrashlytics.getInstance().setCrashlyticsCollectionEnabled(true) somewhere in your app) then it should just work - here's some advice on testing:
https://firebase.google.com/docs/crashlytics/test-implementation?platform=android
So I finally made it..
I'd like to thanks to #cactustictacs for help.
The problem was that I did not integrate Google Play in project settings in Firebase, although it is saying that it is just for Analytics and Subscription.
Before I integrated Google Play in Firebase I tried to add FirebaseCrashlytics.getInstance().setCrashlyticsCollectionEnabled(true) .. it did not work, but I believe it could be usefull to someone.
It wouldn't be such a problem, but it is required to have Owner or Admin permissions on both Firebase account and Google Play console account (which I did not have). After I get the permissions, integration was enabled and I could see test crashes in Crashlytics.
We are develop an iOS app using react-native. And every time there is an update from developer, developer need to build and install on QA phone for testing.
Now, I am trying to use fastlane and firebase app distribution, to distribute new app for QA.
When I create new release, QA got an email notification about that, and they can check it on firebase app distribution. But there is no button for download and install, only message like this.
Device registered!
The developer now needs to update their app to run on your device. You'll get an email when the app is ready to test.
How to make it available to download?
Finally,
For release iOS app to firebase app distribution, you need to generate ad-hoc.
First, u need to create a profiles ad hoc key, u can create it on apple developer or use fastlane to generate it. Then save it inside your project.
Second, set export method inside build app to be ad-hoc.
Third, use get_provisioning_profile to get your profile ad hoc key.
I believe this is very likely because your version is already the same (I think it happened to me recently). Try updating your minor version of the app. (If you are not able to do this for some reason, you can just delete existing build and upload a new one).
I currently have firebase setup and working on my device, I make sure of the storage and real time database and they both work great!
I thought I'd give the robo test a go to see what it does as it mentioned I would not need to add anymore code. Although when attempting to run the robo test with just the default 1 device ( Nexus 5g 23 ) I get the following error:
Normally I would assume I need to go into firebase within Android Studio and setup the gradle to enable this type of testing but the only option I have is the following.
which leads me to the more standard type of testing. I do not believe this is necessary for the Robo lab testing from my understanding (although I may be incorrect).
What's going on how can I use the Robo test? Thanks
This message is probably refering to the APIs enabled for the Firebase project being used to run the tests.
The project selector is shown in the upper-left corner of the Firebase web console (console.firebase.google.com). All of the required APIs are supposed to be enabled when a Firebase project is first created, or when a Google Cloud project is imported into Firebase. It is possible that one of the APIs was disabled or that this process didn't succeed.
Visit https://console.developers.google.com/apis/dashboard?project=your-project-id and take a look at which APIs are enabled. Test Lab uses the "Google Cloud Testing API".
Here is the list of APIs that are enabled for one of the projects that I use for Test Lab.
Im trying to locate the link that is supposed to be created along with my app on Firebase(according to the udacity Firebase course).
I found many links but none of them were accepted by the "after lesson quiz" on udacity.
The content that they have is according to the old UI of Firebase so i cant follow it step by step.
Unfortunately that course is for Firebase 2.x (www.firebase.com) and is out of date. In the legacy Firebase docs, under step 5 : Read & Write to your Firebase Database, you can see that creating a Firebase reference required the actual web address for you app. This is no longer true.
The new and correct way to setup your Firebase app does not require you to use this web address. The steps for setting up a Firebase app now are HERE.
Recently I have Added the my Android and iOS project to Firebase with alpha version.I want to See different Analytic and Crash for Staging and Production. Can anyone help on this.
Thanks
You have several options, depending upon what your needs are. The bottom line is that you should, at the very least, assign different application IDs to the different variants of your app, so they can be separate in the Firebase Console. You can have multiple apps per project (each assigned a different ID), or multiple projects with an app in each one, depending upon what works best for your team and your app.
The actual implementation can get complicated from here on out, so I suggest you read this blog post to learn about the options for your Android app, and how it affects the operation of the various Firebase features in that app.
I think of 2 ways to do so:
Using app version + date range: If you know your app in staging was version X from day N to N+10, you can select theses filter in Firebase analytics to display only the analytics coming from that configuration. This also work for crash reporting.
I prefer: Using a remote config & user property:
Setup in remote config a key as "environment" with some values like "alpha", "beta", "prod". You can then specify the value per platform/app version.
On the phone, read that value in remote config and track a user property in Firebase Analytics that reflect that value.
Finally in the Firebase console you can filter by user property (& app version if necessary).
With this option, when you move an app version out of alpha to beta (for instance) you just need to go in remote config, and change the value for that app version to "beta". This solution doesn't work for crash reporting.
You can use a different Firebase project for each stage so that the analytics are completely distinct. See more on that in the response to this question.
Create a user property Environment, give values such as Dev, Staging and Prod to it on build time.
Change the user property from client side to any of the above three mentioned values based on the build type.
Apply filter by Environment user property on firebase console to see the analytics data.