I wish i could use this feature. I will update the Corona hopefully it will resolve this issue.
Any chance this fix could get rolled into the latest public release? That would be extremely helpful.
I can confirm funda nexus 6 that when signing it with AirSign, the warning goes away and funda sony xperia z4 the build has the correct entitlements.
Agreed. Any forecast on when we can expect this in a public build?
We likely will be doing an interim "beta"build prior to Feb 1, 2015 due to an Apple requirement. I’m assuming this build will include all fixes up to that point. We don’t generally provide dates because there are too many variables in play that can cause us to miss a date, but as a guide, public builds are released about every 3.5 - 4.5 months.
Rob
Was there some kind of regression? I’m using daily 2015.2612 and this is not working for me.
The idea is that this “just works”, right? I don’t have to use AirSign?
I am not aware of any issues with signing in the later daily builds.
Rob
Totally not a Corona problem. Had to get a new provisioning profile from Apple.
Was there some kind of regression? I’m using daily 2015.2612 and this is not working for me.
The idea is that this “just works”, right? I don’t have to use AirSign?
I am not aware of any issues with signing in the later daily builds.
Rob
Totally not a Corona problem. Had to get a new provisioning profile from Apple.
Although I am loathe to append to a long and semi-old forums post, this seems the most appropriate place.
Is anyone seeing this again? I just started seeing this today after several successful uploads earlier in the day, same environment, same app, same everything. Apps just stopped processing, or rather got hung for hours ( 6 + now) and never stopped or completed.
Corona SDK 2015.2751
Running El Capitan
xCode 7.1
Build Certificate has beta-reports-active set to true:
\<key\>aps-environment\</key\> \<string\>production\</string\> \<key\>beta-reports-active\</key\> \<true/\>
At this point, I think this may be an Apple problem…I’m hoping this is just a Apple snafu and will check again in the morning. If it all clears up, I’ll post back.
If you’ve seen this today too, please post back so I know I’m not crazy. :)
All the builds I submitted yesterday and last night got ‘re-queued’ with new submit dates. Also, while some still have the entitlement warning, most do not.
In short, I think the Apple review system is goofed up and probably bogged down with many thousands (+) of jobs by other developers in the same weird states.
Time to wait…
Oh, one binary made it through so at least I can continue testing…
Let’s hope it’s temporary. I’ve gathered this and a couple of other threads and shared them with Engineering to see if there is some commonality to it all.
Rob
I’ll bet it has something to do with the impending release of the iPad Pro. New devices often provoke App Store chaos like this.
And, yeah, please don’t append to old threads. Any info in them is almost certainly useless and any log info posted isn’t worth having as new logs will always have more pertinent detail.
Although I am loathe to append to a long and semi-old forums post, this seems the most appropriate place.
Is anyone seeing this again? I just started seeing this today after several successful uploads earlier in the day, same environment, same app, same everything. Apps just stopped processing, or rather got hung for hours ( 6 + now) and never stopped or completed.
Corona SDK 2015.2751
Running El Capitan
xCode 7.1
Build Certificate has beta-reports-active set to true:
\<key\>aps-environment\</key\> \<string\>production\</string\> \<key\>beta-reports-active\</key\> \<true/\>
At this point, I think this may be an Apple problem…I’m hoping this is just a Apple snafu and will check again in the morning. If it all clears up, I’ll post back.
If you’ve seen this today too, please post back so I know I’m not crazy. :)
All the builds I submitted yesterday and last night got ‘re-queued’ with new submit dates. Also, while some still have the entitlement warning, most do not.
In short, I think the Apple review system is goofed up and probably bogged down with many thousands (+) of jobs by other developers in the same weird states.
Time to wait…
Oh, one binary made it through so at least I can continue testing…
Let’s hope it’s temporary. I’ve gathered this and a couple of other threads and shared them with Engineering to see if there is some commonality to it all.
Rob
I’ll bet it has something to do with the impending release of the iPad Pro. New devices often provoke App Store chaos like this.
And, yeah, please don’t append to old threads. Any info in them is almost certainly useless and any log info posted isn’t worth having as new logs will always have more pertinent detail.