Skip to content
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

[Question] Assert in auth.cc line 119 when trying to create Auth #1680

Open
marcinmalysz opened this issue Dec 20, 2024 · 1 comment
Open

Comments

@marcinmalysz
Copy link

marcinmalysz commented Dec 20, 2024

[REQUIRED] Please fill in the following fields:

  • Pre-built SDK from the website or open-source from this repo: Pre-build SDK
  • Firebase C++ SDK version: 12.1.0
  • Main Firebase Components in concern: Auth (Auth, Database, etc.)
  • Other Firebase Components in use: App,Firestore,Storage (Auth, Database, etc.)
  • Platform you are using the C++ SDK on: Windows (Mac, Windows, or Linux)
  • Platform you are targeting: iOS, Android (iOS, Android, and/or desktop)

[REQUIRED] Please describe the question here:

I was not able to reproduce the issue on test-app where auth example works properly on desktop.

Issue occurs only on Desktop when using c++ wrapper on Windows (Android and iOS works fine)

I'm following general FirebaseApp creation:

m_App = firebase::App::Create();

later on when i try to get Auth by calling this code: (from the same thread)

firebase::App* app = FirebaseApp::Get();
if (!app)
    return nullptr;

firebase::auth::Auth* auth = firebase::auth::Auth::GetAuth(app);
if (!auth)
    return nullptr;

return auth;

I'm getting hard crash with assert from auth.cc line 119

If I try to create auth immediately after creating app i will get a proper object but then calling eg.:

firebase::Future<firebase::auth::AuthResult> result = auth->SignInAnonymously();

Result in exact same assert.

Can you please assist what may be the cause? Is there some kind of releasing object under the hood?

Image
Image
Image

@google-oss-bot
Copy link

I found a few problems with this issue:

  • I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
  • This issue does not seem to follow the issue template. Make sure you provide all the required information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants