Crashlytics: Why doesn't Crashlytics accept an app parameter like other components? #8828
                  
                    
                      sergiocampama
                    
                  
                
                  started this conversation in
                General
              
            Replies: 1 comment
-
| Hey @sergiocampama, we envisioned customers would use the configureWithOptions API to support multiple environments, so they would set the options at startup for their dev / staging / etc apps. We haven't invested in supporting multiple apps because the configureWithOptions flow has worked for users for this use case. For example, we haven't had requests for apps to dynamically change to their development environment at runtime. In addition, supporting multiple apps might be technically challenging with Crashlytics as we don't have an API to tell where to send crash reports. Is there a use case we are missing? | 
Beta Was this translation helpful? Give feedback.
                  
                    0 replies
                  
                
            
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
        
    
Uh oh!
There was an error while loading. Please reload this page.
-
This makes it harder to use Crashlytics in apps that use multiple environments (like development, staging, production), since it always uses the default app.
The other components have APIs like
Auth.auth(app: firebaseApp)that can be used to inject different parameters.Beta Was this translation helpful? Give feedback.
All reactions