Yes of course, I wouldn’t have replied to the thread otherwise
I think it probably happens when there are many textures on the screen, at least in my case I have a lot of images (however on ios6 is working perfectly even on old devices).
Rodrigo, is your app also using a lot of images when you show/hide the mapView?
Another interesting thing is that the problem (textures turning in white rectangles) does not happen when I show the mapView but when I remove it.
Tomorrow I’ll try to create a sample code to reproduce the problem (rodrigo did you also submit a code to reproduce the problem with the bug report? )
I do not do a removeSelf(), I create the mapView and hide it, the mapview is always on top of everything else so it didn’t seem necessary to remove it, when it’s needed I pass it the gps co-ordinates and then show it, the app I’m using it in has 30+ locations that can be shown and seems to work flawlessly. You can take a look if you like.
https://itunes.apple.com/us/app/wheres-bazomb/id537657003?mt=8
Well… yes, the issue is when calling removeSelf() to the mapView. I know i might get away with it by hiding the view… but that doesn’t mean that the problem is not there. Also, there is no issue on ios 6, so there is obviously an issue with the mapView on ios 7.
PXL artificer: no… a lot of textures are not needed to reproduce the issue. I submitted a bug report yesterday with a sample app that all it does is add a mapView on one screen, then uses a tabView to show a different screen. As soon as you call removeSelf() and change the screen, the png for the tabView gets corrupted. No other textures are loaded on the app.
Thanks Rodrigo, I thought it was an unusual issue related to the use of a lot of textures in the app, but since it’s a common issue and easily reproducible I hope it’s going to be easier for Corona engineers figure out the problem.
Hey everyone, sorry for the delay.
I am on iOS 7 GM and latest public build of corona and the issue is not reproducible anymore. The bugs can be closed if needed.
Thanks everyone!
Any updates on this issue?
When we do a new public release we freeze our development process to make sure the build we want to release doesn’t have issues with the things we’ve added and think we’ve fixed. Other bugs that did not make it into the release build of course will still be there. This bug is in that class. It did not make this build. I know @rodrigo.chapuis has filed a bug report, but it wouldn’t hurt if you also file one @PXL artificer. Multiple reports give engineers more information to work with.
Daily builds should start back up soon and then our bug selection process will begin again. We know iOS 7 is about to become a reality and we are interested in collecting these bug reports to help us get a solid iOS7 product out the door.
Thanks Rob.
I just submitted a new bug report, case number: 26039
The bug is easily reproducible, it happens on device as well as simulator.
Update.
Just installed iOS7 GM and this problem is not happening anymore, it looks like Apple fixed this bug.
Rodrigo, is it working correctly for you now?
In case everything’s ok, we can remove the bug report.
Hey everyone, sorry for the delay.
I am on iOS 7 GM and latest public build of corona and the issue is not reproducible anymore. The bugs can be closed if needed.
Thanks everyone!