I have made an app that makes use of CloudKit. One user has recently reported the app to be crashing whenever he uses the feature that interacts with CloudKit. I was able to pin down the issue on him not having enabled "iCloud Drive" in the iCloud settings.
After enabling it, the iPhone app has stopped crashing for him - however on the Watch, whenever it tries to fetch a CKRecord, he is getting the same error message all the time:
CloudKit access was denied by user settings
What else can cause this? The app doesn't have a lot of users but no one so far has reported this issue. Is there a possibility that Apple hasn't thought of syncing this setting with the Watch?
Related
We got a weird case where some users are reporting being blocked from being able to connect to our website which has a Firebase backend.
When the users look at there dev console it firing out ERR_CERT_DATE_INVALID attached to the database point which doesn't make a lot of sense to us why the database would be having what I though is SSL error and only for some users.
I've attached the users are seeing about but haven't been able to repo the issue ourselves
I am testing Firebase SMS authentication on my android app on release mode. So, after few succesful authentications, I started getting the error:
we have blocked all requests from this device due to unusual activity. Try again later
I deleted the affected user but still not working. Then, I contacted Firebase support and that's what they said:
There's a limit of 5 SMS per phone number per 4 hour
Now I am struggling how to test my app before making it live for real users.
I need to test receiving SMS instead of using whitelisted phone numbers. The reason is that I have a bug on release mode which requires many testings to be fixed. Please I need some help!
I have migrated from fabric to firebase by connecting apps via console but I am not getting crash report emails from firebase. I added different users from "Users and Permissions" as suggested here. But I am still not getting email notifications on crash. I tried creating custom role from google cloud console but I am not able to see that in my firebase console. Only case where I am getting mails is when I am adding new user as "Owner" which I think is not right because it would mean I should give full access to all team members. Has anyone faced such issue before?
P.S.: Crashes are logged in console but I am not getting email notifications on crash.
You can configure your email preferences from Alert Settings under the alert icon on the top left of the console. What does this window look like in your firebase console?
Next you need to have at least view permissions on the project to receive e-mail notification. Project owners and editors get email alerts by default. More information on this can be found here.
The Crashlytics dashboard is showing Crash-free statistics but there is no crash in the ISSUES table.
Knowns:
Latest Fabric and Crashlytics following the Firebase tutorial
Forced a crash using Crashlytics.sharedInstance().crash()
In appdelegate I set FirebaseApp.configure()
App is not on Appstore, but I uploaded the dsyms from the xarchive package
That can happen from time and here's why - when a session ends in a crash, the small amount of data that needs to be sent to know that the crash occurred can safely be sent. However, the crash report is larger, so it can't be sent safely until your users relaunch the app. Once your users do that, the crash report will be sent and you'll be able to dive into the details. Let me know if that clears it up or if you have any other questions!
I am having a problem under the following circumstances:
1. Running a webapp with both firebase sdk and angularfire initiated connections
2. App has been running in background. Meaning user has launched other apps. During that time, internet connectivity could have come and gone.
3. User brings webapp back into foreground as active app. Firebase connectivity via angularfire has been lost and updates have been lost as well. Hence "2way" binds to existing views/controllers are not longer current and will not re-establish/sync. Only recovery is to actively kill the app and restart.
This is obviously undesirable. I have currently attempted a bruit force method where I am issuing a goOnline() call at the beginning of each of my controllers in an attempt to always try to re-establish a connection but for services that expect a 2way bind, I am not sure that everything will sync up?
Any thought or guidance on this would be very helpful as this is a serious issue.