[support-octavio]

Hi Mike,

We have identified one new potential problem that we think is at the native level. But we have not yet isolated it yet. Our dev that understands this area deeply has been out the last few days ill. We will update you as soon as we have more info.

[support-octavio]

Hi Mike,

We are still investigating the out of memory issue. We have been trying some different modifications with your app to see if we can better isolate what exactly is happening to cause the memory crash. We are creating a new set of tests as the former tests that we ran last week were not conclusive in isolating the cause. We know this is important to you and will continue working towards a solution. The next 2 weeks are down weeks for our team as many of us are on extended holiday. One of our guys is hoping to work in some investigation. Again we will update you as soon as we know more.

[Mikelv001]

Hi Octavio-

Thank you for the update.

I have three completed updates to my current apps in the iTunes store, and I’m waiting for the fix before I can submit them – all three have the same problem.

Let me know as soon as you know how I should proceed.

Thank you-

Mike

[support-octavio]

Hi Mike,

We are back and have resumed investigation. Will follow up with you as soon as I have more information.

[Mikelv001]

Hi Octavio-

Any updates?

I first posted about this problem November 20; and my app updates have been stopped since.

Any ideas on when you’ll find a fix?

Mike

[support-octavio]

Hi Mike,

We realize this issue has drugout for a while now. We have spent a ton of time on it and set it aside it aside this week to rest brain. Basically it takes a lot of time to change something and then run it until it breaks. The dev team rejected making any internal changes and suggests discontinue use of multiple map widgets and use a single map. We (tech support team) are not so sure and (Michael and I) have been splitting time trying to determine if the map widget is the root cause or if the issue(s) reside somewhere else. We realize reducing the implementation to a single map would be a big change and do not want to recommend that just yet without proving out that it is a worthy effort. But considering you have been blocked for some time you may wish to pursue changing to a single map and see if crashes subside.

[Mikelv001]

Octavio-

Please keep in mind the four apps I have in iTunes right now do not have this problem, and these new updates are for Las Vegas market content only (and changing to the 5 screen size).

Why would there be a problem with multiple maps now?

Mike

[support-octavio]

Hi Mike,

I can understand you concern. A key change is ios7. It is a very different version from ios6. We’ll keep investigating and will follow up when we have an status update.

[Mikelv001]

Octavio-

I just spent 20 minutes and took each spa location screen, and directed each map nav bar to the same map screen, so there would only be one map screen in the app. I rebuilt and tested, and it hasn’t crashed yet.

So I guess that’s a ‘fix’, but the results suck. If I use only one map, direct each nav bar to one map with 30, 60 or 100 icons on one map within each of the apps, the map will be covered, useless and confusing.

Any suggestions?

Mike

[support-octavio]

Hi Mike,

Michael and I built different versions of your app and it does appear the dev team was correct that there is an internal error in how ios7 is handling a large number of google map instances. We have one more angle to investigate that we have referred back to the dev team. We hope to know something early next week, we will keep you updated.

[support-michael]

Some bad news and some good news.

Bad news first.
The use of multiple map widgets is causing your app to crash. We have reviewed old and new versions of the map widget implementation in mobione. And tested a zillion times on a number of ios devices using ios6 and ios7. The app eventually crashes after visiting multiple map widgets. The problem is more pronounced with very large map widget instances. The workaround is to use a single map screen and replace its marker and address dynamically rather than creating new map.

Good news (sort of).
We will be updating the map developer’s guide to discuss alternative approaches. And we have implemented a workaround that uses a single map screen for your app. Octavio or I will send instructions on how to refactor your project to use a single Map screen. It will basically require you to replace all the GotoScreen (yourMapScreen) actions with a RunJavascript that calls a javascript function with the location name. We will follow up by email shortly with detailed instructions.

[Author]

Posts