firebase / firebase/firebase-cpp-sdk
[Question] Assert in auth.cc line 119 when trying to create Auth
- Lingua principale
- C++
- Stelle
- 326
- Fork
- 137
- Merge medio
- 3g 9h
- PR unite (30g)
- 5
Descrizione
### [REQUIRED] Please fill in the following fields:
* Pre-built SDK from the [website](https://firebase.google.com/download/cpp) 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](https://github.com/firebase/firebase-cpp-sdk/blob/main/auth/src/auth.cc#L119)
If I try to create auth immediately after creating app i will get a proper object but then calling eg.:
`firebase::Future 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?



Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Inizia da auth/src/auth.cc alla riga 119 e confronta il flusso desktop Windows segnalato con l’esempio auth funzionante in test-app. Riproduci la sequenza usando App::Create, Auth::GetAuth e SignInAnonymously sullo stesso thread. Il lavoro è completato quando viene identificata la causa dell’assertion e viene documentata o implementata una soluzione verificata per il caso desktop Windows.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- cpp
- Ambito
- authentication
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 25/100