corona199,
Can you tell us which Android device and OS version this error is coming from please?
Odds are this is a bug in Google’s native C/C++ code that we have to work-around. It sounds like you may be running into the Android bug described here…
http://code.google.com/p/android/issues/detail?id=16124
[import]uid: 32256 topic_id: 32451 reply_id: 143405[/import]
Not sure what the current situation with this bug is, but we have just noticed the same error through our error logs on Flurry. Is there a work-around in place yet?
We had emails from 2 users saying that the app crashed on a Xperia Play and a HTC One X, but I’ve no way of knowing which of these devices returned the createWindowSurface failed error (it may even have been an entirely separate device).
It would be handy to know if there is a fix, as our app is currently being featured by Google Play and obviously we want to maximise the opportunity we’ve been given. [import]uid: 84115 topic_id: 32451 reply_id: 144960[/import]
Alan,
The “createWindowSurface” error was fixed in daily build #986. I recommend that you look into using the newest daily build. Or at least daily build #1007 if you’re not ready for our newest widget library changes. [import]uid: 32256 topic_id: 32451 reply_id: 145012[/import]
We built and submitted using daily build #1031, so could something have changed that would cause the problem to reappear? Or if the user was on an older version of Android perhaps?
In the meantime we’ve just excluded those devices from Google Play, but obviously that’s not ideal. [import]uid: 84115 topic_id: 32451 reply_id: 145051[/import]
I’ve confirmed that the fix is still in our code base.
Google Play should be able to tell you what model of Android device that the error came from. Or at least they used to. If you can get us that information, then that would be great. It’s possible that this may just be a device specific issue with a device we haven’t tested with. Sometimes we run into device specific bugs (such as with their OpenGL drivers; the PowerVR GPU being one of them) that we have to work-around on our end. Unfortunately, since Android device hardware can vary so wildly, along with different drivers, and different forked versions of the Android OS… there is no way to future proof the code to work on all hardware. The best we can do is address issues with new Android hardware as they come up.
I’m not aware of any crash issues with the Xperia Play. I just tested it with a sample app today and it ran it without issue. [import]uid: 32256 topic_id: 32451 reply_id: 145108[/import]
On the Crashes & ANRs screen, the Crashes don’t show which devices were involved, and on the only ANR we have it says “Device: Other”.
We also had a review left by someone with a Galaxy SIII saying that the app crashes on the splash screen, but looking at our sales the SIII is the most common device that users have installed the app onto. I presume in that case it must have been an issue with that individual device, so that could also be the case on the Xperia Play, but we have no way of knowing. [import]uid: 84115 topic_id: 32451 reply_id: 145149[/import]
Corona is definitely working on our Galaxy SIII device. And there are plenty of other Corona developers that test with the SIII as well. It’s a popular device. In my opinion, I wouldn’t worry about that one SIII device. For all we know, it might be rooted. In fact, I’m thinking the Android devices coming back as “Other” are likely rooted as well, in which case, anything could be wrong with them such as bad OpenGL drivers that don’t match the GPU hardware.
So far, you’re the only one bringing up the “createWindowSurface failed” error. We believe this issue is solved. If other Corona developers are still seeing it, then I would love to hear their feedback on this because so far we’re no longer getting anymore reports about this error. Perhaps you should start a new forum thread about this specific error to see if others are still running into this? That might be the thing to do. Then we can pool all of our information together and see which devices this still happens on, because I still want to give you the benefit of the doubt.
Not trying to be difficult here. I just don’t have enough information to work on anything yet. I hope this helps. [import]uid: 32256 topic_id: 32451 reply_id: 145225[/import]
Not sure what the current situation with this bug is, but we have just noticed the same error through our error logs on Flurry. Is there a work-around in place yet?
We had emails from 2 users saying that the app crashed on a Xperia Play and a HTC One X, but I’ve no way of knowing which of these devices returned the createWindowSurface failed error (it may even have been an entirely separate device).
It would be handy to know if there is a fix, as our app is currently being featured by Google Play and obviously we want to maximise the opportunity we’ve been given. [import]uid: 84115 topic_id: 32451 reply_id: 144960[/import]
Alan,
The “createWindowSurface” error was fixed in daily build #986. I recommend that you look into using the newest daily build. Or at least daily build #1007 if you’re not ready for our newest widget library changes. [import]uid: 32256 topic_id: 32451 reply_id: 145012[/import]
We built and submitted using daily build #1031, so could something have changed that would cause the problem to reappear? Or if the user was on an older version of Android perhaps?
In the meantime we’ve just excluded those devices from Google Play, but obviously that’s not ideal. [import]uid: 84115 topic_id: 32451 reply_id: 145051[/import]
I’ve confirmed that the fix is still in our code base.
Google Play should be able to tell you what model of Android device that the error came from. Or at least they used to. If you can get us that information, then that would be great. It’s possible that this may just be a device specific issue with a device we haven’t tested with. Sometimes we run into device specific bugs (such as with their OpenGL drivers; the PowerVR GPU being one of them) that we have to work-around on our end. Unfortunately, since Android device hardware can vary so wildly, along with different drivers, and different forked versions of the Android OS… there is no way to future proof the code to work on all hardware. The best we can do is address issues with new Android hardware as they come up.
I’m not aware of any crash issues with the Xperia Play. I just tested it with a sample app today and it ran it without issue. [import]uid: 32256 topic_id: 32451 reply_id: 145108[/import]
On the Crashes & ANRs screen, the Crashes don’t show which devices were involved, and on the only ANR we have it says “Device: Other”.
We also had a review left by someone with a Galaxy SIII saying that the app crashes on the splash screen, but looking at our sales the SIII is the most common device that users have installed the app onto. I presume in that case it must have been an issue with that individual device, so that could also be the case on the Xperia Play, but we have no way of knowing. [import]uid: 84115 topic_id: 32451 reply_id: 145149[/import]
Corona is definitely working on our Galaxy SIII device. And there are plenty of other Corona developers that test with the SIII as well. It’s a popular device. In my opinion, I wouldn’t worry about that one SIII device. For all we know, it might be rooted. In fact, I’m thinking the Android devices coming back as “Other” are likely rooted as well, in which case, anything could be wrong with them such as bad OpenGL drivers that don’t match the GPU hardware.
So far, you’re the only one bringing up the “createWindowSurface failed” error. We believe this issue is solved. If other Corona developers are still seeing it, then I would love to hear their feedback on this because so far we’re no longer getting anymore reports about this error. Perhaps you should start a new forum thread about this specific error to see if others are still running into this? That might be the thing to do. Then we can pool all of our information together and see which devices this still happens on, because I still want to give you the benefit of the doubt.
Not trying to be difficult here. I just don’t have enough information to work on anything yet. I hope this helps. [import]uid: 32256 topic_id: 32451 reply_id: 145225[/import]