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
I am experiencing an issue with the compass functionality on iOS. Specifically, the compass does not display and remains stuck on a loading indicator on AsyncSnapshot<LocationStatus>. There are no error messages printed to the console.
Here are some additional details about the issue:
Location services are enabled and permission has been granted.
The issue is specific to iOS; the compass works as expected on other platforms.
The device is running the latest version of iOS.
The issue occurs consistently and cannot be resolved by restarting the app or the device.
I have attempted to troubleshoot the issue by checking the relevant permissions and reviewing the code that relates to the compass functionality, but so far I have not been able to identify the root cause of the issue.
I would greatly appreciate any assistance in resolving this issue, as the compass functionality is a critical feature of our app. Thank you in advance for your help.
The text was updated successfully, but these errors were encountered:
I apologize for any confusion caused. After testing the app on a real iPhone, I found that it works fine. It seems that the issue I was experiencing was specific to the iOS simulator.
Please go ahead and close this issue. However, I wanted to suggest adding a note to the README file indicating that the app may not work properly in the iOS simulator.
I am experiencing an issue with the compass functionality on iOS. Specifically, the compass does not display and remains stuck on a loading indicator on
AsyncSnapshot<LocationStatus>
. There are no error messages printed to the console.Here are some additional details about the issue:
I would greatly appreciate any assistance in resolving this issue, as the compass functionality is a critical feature of our app. Thank you in advance for your help.
The text was updated successfully, but these errors were encountered: