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
We have encountered a customer who's iOS app repeatedly crashes after naming a trying to name a particle device. The particle backend knows this device is online, and it does not have a name. Names have been:
"doggy ADHD" (which had a space)
"Logic_dogs" (with no space)
random default of two words with an underscore
Customer says:
"But after I hit "OK" on that screen, the app crashes out to my main home screen."
Device is iOS 9.3.2.
Notably, the users photon is online, and they did get an OTA updating to v24 of our software. From our dashboard we see:
Interestingly, the name is "none" which seems consistent with the user reporting an error crashing immediately after attempting to name. It appears the "name" never got there. We keep track of errors via FailedPairingRecords, but we do not have any in this case, as the app has crashed before we get the error code back.
The text was updated successfully, but these errors were encountered:
Really sorry for late reply - Can you pinpoint me to where exactly does the crash occur and what kind of error? Is it while calling the Spark-SDK rename method?
We have encountered a customer who's iOS app repeatedly crashes after naming a trying to name a particle device. The particle backend knows this device is online, and it does not have a name. Names have been:
"doggy ADHD" (which had a space)
"Logic_dogs" (with no space)
random default of two words with an underscore
Customer says:
"But after I hit "OK" on that screen, the app crashes out to my main home screen."
Device is iOS 9.3.2.
Notably, the users photon is online, and they did get an OTA updating to v24 of our software. From our dashboard we see:
290048001047353138383138 none v24 real_email_removed@gmail.com Jun 22nd 2016 at 4:00 pm
Interestingly, the name is "none" which seems consistent with the user reporting an error crashing immediately after attempting to name. It appears the "name" never got there. We keep track of errors via FailedPairingRecords, but we do not have any in this case, as the app has crashed before we get the error code back.
The text was updated successfully, but these errors were encountered: