It will be investigated. As always, a bug report remains the most effective way to report issues like these, especially when dealing with very device-specific and OS-specific issues of this nature.
@Brent, I haven’t had a chance to check yet, but from what RLRL said above the bug appears to be fixed as of the latest daily build and building for iOS 7.1 beta, so there isn’t really a bug to report at this time. The problem as I see it isn’t so much the bug itself but the fact that the CL fix is only temporary. Whenever Apple releases a new version of iOS the fix no longer works, thousands of my own paying customers get a crashing app with reduced functionality, and I have to wait for CL to presumably copy/paste whatever the old fix was to the new iOS beta so I can finally have the joy of rebuilding and publishing an update.
From my understanding the CL fix for this issue was made intentionally temporary as it was viewed as an Apple bug that would be fixed in the next release. But this is the third iOS update where the bug has surfaced so I think it’s fair to say Apple has no intention of fixing it on their end, so perhaps it would be best if CL made their own fix permanent.
Thanks for listening.
Hi @HardBoiledIndustries,
This is a legitimate concern so we’re investigating how to both fix it and implement a more robust solution (versus these flags). I don’t know the details yet, but most likely it will involved dropping support for iOS 5.x. I’ll keep you posted on the progress as I hear it from engineering.
Take care,
Brent
Hi Brent,
Glad to know your engineers are investigating a better solution. Do you have a ballpark timeframe? The reason I ask is I need to create an update to my iOS app that is now crashing due to the above issue, but if I use the temp fix now it’s just going to break again when a new update to iOS comes out, and then I’ll have to push out another update when you guys do deliver the better fix. If it’s a matter of waiting a couple weeks or so I will hold out and do it the right way once, but if you think it’s going to be further out than that I’ll probably have to make do with the temp fix sooner. Thanks for any info. you can provide.
-Stephen
Hi Stephen,
I’m checking into this, and the enhanced, more robust fix does not appear to be imminent (as in, next 1-2 weeks), so it’s probably better if you use a temporary workaround.
In the meantime, we really need a bug report for this. Essentially, it keeps the issue on our radar and provides a method for us to track it… we just can’t effectively track issues that reside solely in forum threads.
Thanks,
Brent
In iOS 7.1 this is again not working, also not with:
CoronaUseIOS7IPadPhotoPickerLandscapeOnlyWorkaround = true,
CoronaUseIOS6IPadPhotoPickerLandscapeOnlyWorkaround = true,
CoronaUseIOS7LandscapeOnlyWorkaround = true,
CoronaUseIOS6LandscapeOnlyWorkaround = true,
Open the camera = immediate crash
It only works with portrait enabled, which makes my app useless!
I don’t expect any reponse anyhow from Corona staff, there is no support whatsoever and this annoying bug will remain forever, like always with Corona.
Hi @RLRL,
Others are seemingly not having any issues with this, so we’d need an official bug report which shows it clearly happening, and on which device(s).
Brent
The latest daily build and compile for 7.1 beta fixes the issue. However it does break my current app for users that have been updated to iOS 7.1 on iPhone 4S.
Ugh. Same issue here, previously working apps on existing users’ devices are now crashing when opening the camera and/or photo library on iPhones upgraded to iOS 7.1.
This “workaround” seems pretty kludgy if you ask me. Weird syntax, stops working and breaks published apps whenever there’s a major (or now point) upgrade to iOS. Corona Labs has to create a new workaround each time it breaks (why does it keep falling through CL’s regression testing cracks?), and now I have to drop everything and push out an update on an existing app. Surely there must be a better way to fix this?
It seems others *do* have issues with this.
It will be investigated. As always, a bug report remains the most effective way to report issues like these, especially when dealing with very device-specific and OS-specific issues of this nature.
@Brent, I haven’t had a chance to check yet, but from what RLRL said above the bug appears to be fixed as of the latest daily build and building for iOS 7.1 beta, so there isn’t really a bug to report at this time. The problem as I see it isn’t so much the bug itself but the fact that the CL fix is only temporary. Whenever Apple releases a new version of iOS the fix no longer works, thousands of my own paying customers get a crashing app with reduced functionality, and I have to wait for CL to presumably copy/paste whatever the old fix was to the new iOS beta so I can finally have the joy of rebuilding and publishing an update.
From my understanding the CL fix for this issue was made intentionally temporary as it was viewed as an Apple bug that would be fixed in the next release. But this is the third iOS update where the bug has surfaced so I think it’s fair to say Apple has no intention of fixing it on their end, so perhaps it would be best if CL made their own fix permanent.
Thanks for listening.
Hi @HardBoiledIndustries,
This is a legitimate concern so we’re investigating how to both fix it and implement a more robust solution (versus these flags). I don’t know the details yet, but most likely it will involved dropping support for iOS 5.x. I’ll keep you posted on the progress as I hear it from engineering.
Take care,
Brent
Hi Brent,
Glad to know your engineers are investigating a better solution. Do you have a ballpark timeframe? The reason I ask is I need to create an update to my iOS app that is now crashing due to the above issue, but if I use the temp fix now it’s just going to break again when a new update to iOS comes out, and then I’ll have to push out another update when you guys do deliver the better fix. If it’s a matter of waiting a couple weeks or so I will hold out and do it the right way once, but if you think it’s going to be further out than that I’ll probably have to make do with the temp fix sooner. Thanks for any info. you can provide.
-Stephen
Hi Stephen,
I’m checking into this, and the enhanced, more robust fix does not appear to be imminent (as in, next 1-2 weeks), so it’s probably better if you use a temporary workaround.
In the meantime, we really need a bug report for this. Essentially, it keeps the issue on our radar and provides a method for us to track it… we just can’t effectively track issues that reside solely in forum threads.
Thanks,
Brent
Now, CoronaUseIOS7LandscapeOnlyWorkaround is working.
I use Corona 2299,
probably CoronaUseIOS7LandscapeOnlyWorkaround is fixed
Now, CoronaUseIOS7LandscapeOnlyWorkaround is working.
I use Corona 2299,
probably CoronaUseIOS7LandscapeOnlyWorkaround is fixed
I’m seeing this again now we have iOS 8 in the mix. Ideas on workaround?
Yep, me too.
should we get an update with CoronaUseIOS8LandscapeOnlyWorkaround or is there something else?
Hi all,
Engineering is aware of this. I don’t know what the solution will be, i.e. a “workaround” or something more comprehensive. In any case, please bear with us as we iron out the known iOS8 issues.
Thanks,
Brent