Scenic 3 App crash after start
Quote from satmax on 30.10.2021, 01:17HI,
when I start scenic 3, after a few seconds the map is shown and at this time the apps crashes. I can't make any input...
Before I had created one new tour and downloaded one Map (Austria).
What can I do? A full deinstall and install new?
HI,
when I start scenic 3, after a few seconds the map is shown and at this time the apps crashes. I can't make any input...
Before I had created one new tour and downloaded one Map (Austria).
What can I do? A full deinstall and install new?
Quote from satmax on 30.10.2021, 02:38After a full reinstall I lost my pictures for driver and bikes, not a big problem, but it was nice to have when you can also restore this pictures and some settings...
After a full reinstall I lost my pictures for driver and bikes, not a big problem, but it was nice to have when you can also restore this pictures and some settings...
Quote from Guido on 30.10.2021, 06:56It sounds like your account had a syncing problem even before Scenic 3. This could explain the crash and also the fact that you didn’t have the pictures (as picture normally do sync). Settings indeed are not synced.
let me know if you run into any more problems. Apologies for the inconvenience and best regards,
Guido
It sounds like your account had a syncing problem even before Scenic 3. This could explain the crash and also the fact that you didn’t have the pictures (as picture normally do sync). Settings indeed are not synced.
let me know if you run into any more problems. Apologies for the inconvenience and best regards,
Guido
Quote from GHJ on 30.10.2021, 08:02After the update to Scenic 3 on my iPhone the app crashed frequently. I deleted and reinstalled the app. After login all content came back. It seems to be very stable now.
After the update to Scenic 3 on my iPhone the app crashed frequently. I deleted and reinstalled the app. After login all content came back. It seems to be very stable now.
Quote from OMR on 31.10.2021, 14:37Here too... after update to Scenic 3 the app crashed sometimes... after reinstall i can not log in... the app is crashing every time when i tip on login button
Here too... after update to Scenic 3 the app crashed sometimes... after reinstall i can not log in... the app is crashing every time when i tip on login button
Quote from Guido on 31.10.2021, 14:57Sorry. This is a bug affecting some users. We missed this one during testing. An update is currently awaiting approval from Apple, which solves the problem. Unfortunately, Apple needs a few days to approve an update.
Sorry. This is a bug affecting some users. We missed this one during testing. An update is currently awaiting approval from Apple, which solves the problem. Unfortunately, Apple needs a few days to approve an update.
Quote from Guido on 01.11.2021, 08:25Version 3.01 was released yesterday. Could you give it a try with that version please? (Perhaps you'll need to manually go to the App Store to make sure you have the latest version).
Version 3.01 was released yesterday. Could you give it a try with that version please? (Perhaps you'll need to manually go to the App Store to make sure you have the latest version).
Quote from Shapa on 01.11.2021, 10:33The same issue for me - it is crashing after start (in a few seconds). The new version did not fix the issue. App delete/reinstall worked until I configured settings. Maybe it is related to the "cameras" layer enabled.
The same issue for me - it is crashing after start (in a few seconds). The new version did not fix the issue. App delete/reinstall worked until I configured settings. Maybe it is related to the "cameras" layer enabled.
Quote from Guido on 01.11.2021, 10:35Quote from Shapa on 01.11.2021, 10:33The same issue for me - it is crashing after start (in a few seconds). The new version did not fix the issue. App delete/reinstall worked until I configured settings. Maybe it is related to the "cameras" layer enabled.
Yes... that could be it definitely. There are some problems with very big POI groups displaying on the map. I'm still looking into this. For what it's worth... I will be adding Speed Cameras 'out of the box' in the near future... so no more need for these big POI groups.
Quote from Shapa on 01.11.2021, 10:33The same issue for me - it is crashing after start (in a few seconds). The new version did not fix the issue. App delete/reinstall worked until I configured settings. Maybe it is related to the "cameras" layer enabled.
Yes... that could be it definitely. There are some problems with very big POI groups displaying on the map. I'm still looking into this. For what it's worth... I will be adding Speed Cameras 'out of the box' in the near future... so no more need for these big POI groups.
Quote from AstridM on 01.11.2021, 16:38Quote from Guido on 01.11.2021, 10:35Quote from Shapa on 01.11.2021, 10:33The same issue for me - it is crashing after start (in a few seconds). The new version did not fix the issue. App delete/reinstall worked until I configured settings. Maybe it is related to the "cameras" layer enabled.
Yes... that could be it definitely. There are some problems with very big POI groups displaying on the map. I'm still looking into this. For what it's worth... I will be adding Speed Cameras 'out of the box' in the near future... so no more need for these big POI groups.
Can you specific „very big POI groups“?
Quote from Guido on 01.11.2021, 10:35Quote from Shapa on 01.11.2021, 10:33The same issue for me - it is crashing after start (in a few seconds). The new version did not fix the issue. App delete/reinstall worked until I configured settings. Maybe it is related to the "cameras" layer enabled.
Yes... that could be it definitely. There are some problems with very big POI groups displaying on the map. I'm still looking into this. For what it's worth... I will be adding Speed Cameras 'out of the box' in the near future... so no more need for these big POI groups.
Can you specific „very big POI groups“?
Quote from Guido on 01.11.2021, 16:42It's not only the POI group, but also what device you are on and how many other apps are 'open' in the background. Older devices have less memory available and will crash sooner. Working on a solution to make these big poi groups less memory intensive.
On average, I'd day, every group with > 1000 POIs can be problematic. On very old devices maybe > 500.
It's not only the POI group, but also what device you are on and how many other apps are 'open' in the background. Older devices have less memory available and will crash sooner. Working on a solution to make these big poi groups less memory intensive.
On average, I'd day, every group with > 1000 POIs can be problematic. On very old devices maybe > 500.
Quote from AstridM on 01.11.2021, 16:55A crash happens on my iPad pro (latest iPad OS) when I select a specific holder in recorded rides. In this case I can simply start the app again and everything works (except selecting the mentioned folder). It gets worse, when I select that very same folder in „show on map“. Then the app goes into a crash loop so that I have to de-install and re-install from scratch.
The folder contains 75 rides. I was able to find the one ride which is causing the issue. Isolating that file to another folder helps as I can use the folder now containing 74 rides as intended. But when I do the same as described above with the folder containing only the one (isolated) ride, the very same issues happen again. This is reproducable.
While I know that a faulty file could cause some troubles, I need to mention that the same folder containing the „faulty“ file works perfectly well on the iPhone 13 pro max (also with the latest iOS).
A crash happens on my iPad pro (latest iPad OS) when I select a specific holder in recorded rides. In this case I can simply start the app again and everything works (except selecting the mentioned folder). It gets worse, when I select that very same folder in „show on map“. Then the app goes into a crash loop so that I have to de-install and re-install from scratch.
The folder contains 75 rides. I was able to find the one ride which is causing the issue. Isolating that file to another folder helps as I can use the folder now containing 74 rides as intended. But when I do the same as described above with the folder containing only the one (isolated) ride, the very same issues happen again. This is reproducable.
While I know that a faulty file could cause some troubles, I need to mention that the same folder containing the „faulty“ file works perfectly well on the iPhone 13 pro max (also with the latest iOS).
Quote from Guido on 01.11.2021, 16:59
Quote from AstridM on 01.11.2021, 16:55A crash happens on my iPad pro (latest iPad OS) when I select a specific holder in recorded rides. In this case I can simply start the app again and everything works (except selecting the mentioned folder). It gets worse, when I select that very same folder in „show on map“. Then the app goes into a crash loop so that I have to de-install and re-install from scratch.
The folder contains 75 rides. I was able to find the one ride which is causing the issue. Isolating that file to another folder helps as I can use the folder now containing 74 rides as intended. But when I do the same as described above with the folder containing only the one (isolated) ride, the very same issues happen again. This is reproducable.
While I know that a faulty file could cause some troubles, I need to mention that the same folder containing the „faulty“ file works perfectly well on the iPhone 13 (also with the latest iOS).
What's the name of the ride, and your Scenic nickname? I suspect the ride got corrupted. Did you record that ride on the iPhone 13?
Quote from AstridM on 01.11.2021, 16:55A crash happens on my iPad pro (latest iPad OS) when I select a specific holder in recorded rides. In this case I can simply start the app again and everything works (except selecting the mentioned folder). It gets worse, when I select that very same folder in „show on map“. Then the app goes into a crash loop so that I have to de-install and re-install from scratch.
The folder contains 75 rides. I was able to find the one ride which is causing the issue. Isolating that file to another folder helps as I can use the folder now containing 74 rides as intended. But when I do the same as described above with the folder containing only the one (isolated) ride, the very same issues happen again. This is reproducable.
While I know that a faulty file could cause some troubles, I need to mention that the same folder containing the „faulty“ file works perfectly well on the iPhone 13 (also with the latest iOS).
What's the name of the ride, and your Scenic nickname? I suspect the ride got corrupted. Did you record that ride on the iPhone 13?
Quote from AstridM on 01.11.2021, 17:00Quote from Guido on 01.11.2021, 16:42It's not only the POI group, but also what device you are on and how many other apps are 'open' in the background. Older devices have less memory available and will crash sooner. Working on a solution to make these big poi groups less memory intensive.
On average, I'd day, every group with > 1000 POIs can be problematic. On very old devices maybe > 500.
Thanks for the very quick answer which helps a lot.
Quote from Guido on 01.11.2021, 16:42It's not only the POI group, but also what device you are on and how many other apps are 'open' in the background. Older devices have less memory available and will crash sooner. Working on a solution to make these big poi groups less memory intensive.
On average, I'd day, every group with > 1000 POIs can be problematic. On very old devices maybe > 500.
Thanks for the very quick answer which helps a lot.
Quote from AstridM on 01.11.2021, 17:04Quote from Guido on 01.11.2021, 16:59
Quote from AstridM on 01.11.2021, 16:55A crash happens on my iPad pro (latest iPad OS) when I select a specific holder in recorded rides. In this case I can simply start the app again and everything works (except selecting the mentioned folder). It gets worse, when I select that very same folder in „show on map“. Then the app goes into a crash loop so that I have to de-install and re-install from scratch.
The folder contains 75 rides. I was able to find the one ride which is causing the issue. Isolating that file to another folder helps as I can use the folder now containing 74 rides as intended. But when I do the same as described above with the folder containing only the one (isolated) ride, the very same issues happen again. This is reproducable.
While I know that a faulty file could cause some troubles, I need to mention that the same folder containing the „faulty“ file works perfectly well on the iPhone 13 (also with the latest iOS).
What's the name of the ride, and your Scenic nickname? I suspect the ride got corrupted. Did you record that ride on the iPhone 13?
The ride was recorded on an iPhone 11 pro max (now replaced by 13 pro max) The ride name is „Ride of 2021-08-21 18:15“ and the nickname is astridm.
Quote from Guido on 01.11.2021, 16:59
Quote from AstridM on 01.11.2021, 16:55A crash happens on my iPad pro (latest iPad OS) when I select a specific holder in recorded rides. In this case I can simply start the app again and everything works (except selecting the mentioned folder). It gets worse, when I select that very same folder in „show on map“. Then the app goes into a crash loop so that I have to de-install and re-install from scratch.
The folder contains 75 rides. I was able to find the one ride which is causing the issue. Isolating that file to another folder helps as I can use the folder now containing 74 rides as intended. But when I do the same as described above with the folder containing only the one (isolated) ride, the very same issues happen again. This is reproducable.
While I know that a faulty file could cause some troubles, I need to mention that the same folder containing the „faulty“ file works perfectly well on the iPhone 13 (also with the latest iOS).
What's the name of the ride, and your Scenic nickname? I suspect the ride got corrupted. Did you record that ride on the iPhone 13?
The ride was recorded on an iPhone 11 pro max (now replaced by 13 pro max) The ride name is „Ride of 2021-08-21 18:15“ and the nickname is astridm.
Quote from Guido on 01.11.2021, 17:20The ride was recorded on an iPhone 11 pro max (now replaced by 13 pro max) The ride name is „Ride of 2021-08-21 18:15“ and the nickname is astridm.
It is as I suspected. Some data of this ride got corrupted when it was synced to the server. I suspect you installed the 13pro with a backup of the 11 pro, correct?So, only the device where the ride was originally recorded (or the device that was restored from a backup from that device) will have a 'good' version of this ride. All other devices, that were synced via the server, will have the 'bad' copy.Unfortunately there is nothing I can do about this. I recommend to remove the ride so that it doesn't cause any more problems. Or, if you prefer, I can move the ride for you.
The ride was recorded on an iPhone 11 pro max (now replaced by 13 pro max) The ride name is „Ride of 2021-08-21 18:15“ and the nickname is astridm.
Quote from Shapa on 01.11.2021, 17:29So I can confirm - it is crashing because of the Speed Cameras layer. In case it is switched off, no crashes anymore. Anyway, the map is very slow in comparison to the previous version, I had to wait for ~3-4 seconds until the main screen will become responsible. iPhone 13 Pro Max 1TB...
When I'm trying to access my POI (speedcams, ~15000), the app is crashing as well.
So I can confirm - it is crashing because of the Speed Cameras layer. In case it is switched off, no crashes anymore. Anyway, the map is very slow in comparison to the previous version, I had to wait for ~3-4 seconds until the main screen will become responsible. iPhone 13 Pro Max 1TB...
When I'm trying to access my POI (speedcams, ~15000), the app is crashing as well.
Quote from Guido on 01.11.2021, 17:33Quote from Shapa on 01.11.2021, 17:29So I can confirm - it is crashing because of the Speed Cameras layer. In case it is switched off, no crashes anymore. Anyway, the map is very slow in comparison to the previous version, I had to wait for ~3-4 seconds until the main screen will become responsible. iPhone 13 Pro Max 1TB...
When I'm trying to access my POI (speedcams, ~15000), the app is crashing as well.
Correct in the POIs. I found the cause and working on a fix. See a few posts above.
The map should not load this slow if you turn off the big POI layers . Maybe only the first time, but after that it should load instantly.
Quote from Shapa on 01.11.2021, 17:29So I can confirm - it is crashing because of the Speed Cameras layer. In case it is switched off, no crashes anymore. Anyway, the map is very slow in comparison to the previous version, I had to wait for ~3-4 seconds until the main screen will become responsible. iPhone 13 Pro Max 1TB...
When I'm trying to access my POI (speedcams, ~15000), the app is crashing as well.
Correct in the POIs. I found the cause and working on a fix. See a few posts above.
The map should not load this slow if you turn off the big POI layers . Maybe only the first time, but after that it should load instantly.
Quote from AstridM on 02.11.2021, 01:43Quote from Guido on 01.11.2021, 17:20The ride was recorded on an iPhone 11 pro max (now replaced by 13 pro max) The ride name is „Ride of 2021-08-21 18:15“ and the nickname is astridm.
It is as I suspected. Some data of this ride got corrupted when it was synced to the server. I suspect you installed the 13pro with a backup of the 11 pro, correct?So, only the device where the ride was originally recorded (or the device that was restored from a backup from that device) will have a 'good' version of this ride. All other devices, that were synced via the server, will have the 'bad' copy.Unfortunately there is nothing I can do about this. I recommend to remove the ride so that it doesn't cause any more problems. Or, if you prefer, I can move the ride for you.
Thanks a lot for your investigation and clarification. I will remove the ride myself.
Quote from Guido on 01.11.2021, 17:20The ride was recorded on an iPhone 11 pro max (now replaced by 13 pro max) The ride name is „Ride of 2021-08-21 18:15“ and the nickname is astridm.
It is as I suspected. Some data of this ride got corrupted when it was synced to the server. I suspect you installed the 13pro with a backup of the 11 pro, correct?So, only the device where the ride was originally recorded (or the device that was restored from a backup from that device) will have a 'good' version of this ride. All other devices, that were synced via the server, will have the 'bad' copy.Unfortunately there is nothing I can do about this. I recommend to remove the ride so that it doesn't cause any more problems. Or, if you prefer, I can move the ride for you.
Thanks a lot for your investigation and clarification. I will remove the ride myself.
