rizafran

Hi @shamiul110107, it looks like your issue is related to #11732. Does updating the SDK to 10.13.0 or later fixes the issue?

Sorry for the late revert, could you provide your full stack trace of the issue? Based on the stack trace you shared initially, it seems like there are missing UUIDs...

Hi @gpfister, it seems like what you're encountering is an intended behavior. Firebase Auth uses method swizzling to automatically obtain APNs token. You'll be able to obtain APNs token manually...

Hi @RajanSingh2022, as mentioned [here](https://github.com/firebase/firebase-ios-sdk/issues/9316#issuecomment-1034075978), the error message `std::bad_alloc` suggests a C++ allocation failed, possibly due to memory pressure. With this, could you try profiling your app for memory leaks...

Thanks for the info, @RajanSingh2022. Could you try to profile your app via Xcode instruments and share the trace here to investigate?

Hi @johnfrancmartin, per checking, it looks like API key restrictions must be removed in order for the reCAPTCHA to work. See #7653 for more info.

Thanks for reporting, @DancingWind. I tried to reproduce the issue by setting the `FirebaseAutomaticScreenReportingEnabled` flag to `NO`, but the automated screen_views were not showing in my logs. May I know...

@DancingWind, I also tried to disable calling the event that manually logs my screen_view, but the screen_view was not showing in my logs when `FirebaseAutomaticScreenReportingEnabled` is set to `NO`. Could...

Hi @yqiang, upon checking the [docs](https://cloud.google.com/identity-platform/docs/admin/email-enumeration-protection#overview), you need to use the `verifyBeforeUpdateEmail` as your users can no longer update their email with the `updateEmail()` method when the enumeration protection feature...

Hi @moyerr, I tried to reproduce the issue using the code snippet you shared, but I'm able to see my network requests in the console. Could you provide an [MCVE](https://stackoverflow.com/help/minimal-reproducible-example)...