Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 23

Thread: [iOS 3.0.3] While navigating, memory keeps growing until iOS kills my app.

  1. #11
    Etablierter skobbler
    Join Date
    15.03.2017
    Posts
    11
    It's the memory issue – app is not crashing, but killed by the OS.

  2. #12
    Erfahrener skobbler
    Join Date
    11.02.2015
    Posts
    123
    Hi Adrian,

    Cobi is confirming the feeling I've had for a long time and is also in line with user feedback I've gotten. If the SDK is in offline mode crashes are far less frequent and sometimes even gone. The memory grows a lot when the SDK connects to the server for map data. My guess is the 'big' leaks are caused by the networking code. Hope this helps.

    Cheers,
    Guido

  3. #13
    Etablierter skobbler
    Join Date
    15.03.2017
    Posts
    11
    I can confirm that this is a clear pattern in bug reports by our users – bad / spotty connectivity in areas with uncached map tiles (download is triggered) OR rerouting (routing request is triggered).

  4. #14
    Erfahrener skobbler
    Join Date
    11.02.2015
    Posts
    123
    Any progress on this? As far as I'm concerned this is the number 1 issue the SDK has at the moment. Navigation is one of the key features of the SDK and if it crashes during navigation.. well.
    As I've shown you in the email exchange we had, the demo app also shows this behaviour. 9 crashes in 4 hours of navigating.

    I've now adjusted my own app to use offline maps only while navigating (I put the SDK in offline mode during navigation). Crashes are gone!
    This is costing me money because I now have to give the offline maps away for free, as they are mandatory for the app to work now. So, forgive me for pushing so hard to get this fixed, but it's really important to me, and I'm guessing all SDK users that use Online Navigation.

  5. #15
    Etablierter skobbler
    Join Date
    15.03.2017
    Posts
    11
    Some of our users have started disabling "Mobile Data" for the app so that it doesn't crash anymore. Very embarrassing.

  6. #16
    Etablierter skobbler
    Join Date
    15.03.2017
    Posts
    11
    Someone in our team noticed this crash for the first-time ever – lo-and-behold – on the day he received a text message from his carrier that mobile data will be throttled. It's crystal-clear that there is a problem in the iOS wrappers' networking code.

  7. #17
    Erfahrener skobbler
    Join Date
    11.02.2015
    Posts
    123
    I'm thinking about switching to the HERE SDK. Many SDK bugs that I need to work around. Would like to stick to Skobbler though, if improvements are made. Not sure what the migration of the SDK is going to bring us. @Adrian: anything you can tell us about that?

  8. #18
    Erfahrener skobbler
    Join Date
    12.09.2016
    Posts
    112
    Obviously, the new SDK will bring a stack of improvements. The only thing is that it will be available in a year or so, as it's still under development phase. For this particular issue we don't have a solution at this point, as our dev could not reproduce it, in simulation scenarios as well as under several drive tests we've made.

  9. #19
    Erfahrener skobbler
    Join Date
    11.02.2015
    Posts
    123
    OK. I know it's difficult to reproduce, but I think I've proven that it's an issue with the SDK, as also your own demo app crashed multiple times during a 4 hour ride. If I would be the only one with this issue I would also doubt it was the SDK, but I'm not. If you need more info, please let me know. Will you still be bringing out updates/hotfixes to the current version of the SDK, since the migrated SDK is a year out?

  10. #20
    Erfahrener skobbler
    Join Date
    12.09.2016
    Posts
    112
    Yes, of course, we will continue to support our current users with updates&hotfixes to the current SDK for all this period.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •