You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maps SDK Version: Attached in the following screenshot 👇🏻
Observed behavior and steps to reproduce
Just play with the SDK using the SearchEngine feature. The crash has only occurred for 1 user so far. It hasn't happened frequently enough to be significant... (For now)
Expected behavior
No crash. Should use weak or handle the unowned references in a proper way.
Additional links and references
The text was updated successfully, but these errors were encountered:
juansanzone
changed the title
SDK Crash : DefaultLocationProvider.swift - Attempted to read an unowned reference but object was already deallocated bug 🪲
SDK Crash : DefaultLocationProvider.swift - Attempted to read an unowned reference but object was already deallocated
Apr 29, 2024
Hi @juansanzone, when you instantiate a SearchEngine are you owning the reference to that or are you letting it expire within the lifetime of the usage? For example if you entering a function, creating a SearchEngine, invoking a search/suggest/retrieve function on it, and destroying the local reference to the SearchEngine then the search/suggest/retrieve operation will likely still be running after the function exits and that operation and associated objects (LocationProvider) will no longer have a SearchEngine to report results back to.
Environment
Observed behavior and steps to reproduce
SearchEngine
feature. The crash has only occurred for 1 user so far. It hasn't happened frequently enough to be significant... (For now)Expected behavior
No crash. Should use
weak
or handle theunowned
references in a proper way.Additional links and references
The text was updated successfully, but these errors were encountered: