For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 14 replies, 5 voices, and was last updated 12 years, 5 months ago by
.
-
Posts
-
Update: I am getting the exact same error now:
Application Failed Codesign verification. The signature was invalid, contains disallowed entitlements, or it was not signed with an iPhone Distribution Certificate.Unable to extract codesigning entitlements form your application. Please make sure — is a valid Mach executable that’s properly codesigned.
—————————I tried to upload a new app today. It keep failing with the Distro certificate so I even created a new one along with a new provisining file and I get this error.
Application Failed Codesign verification. The signature was invalid, contains disallowed entitlements, or it was not signed with an iPhone Distribution Certificate.
Unable to extract codesigning entitlements form your application. Please make sure — is a valid Mach executable that’s properly codesigned.
I did also have a couple times where it could not connect to the build server, so I dont know if that will have anything to do with it. It is build number 4808003 was the latest try of several.
UPDATE: It must of had something to do with the errors from the service. I tried today and it built fine and uploaded to the store just fine also.
Marking as closed.Hi I currently have this error and have tried at least 20 times to fix it but still cannot so if someone has any idea I would appreciate a work around because at present my app is stuck in limbo
@robert65
Make sure you are using the latest Application Uploader. Ever since I upgraded I have not gotten this error.Cincy, I have been sending my apps via the 3rd party upload and to be fair Kyle has been very supportive of my dilemma, and I cant thank him enough for taking the time too try and fix my issue, it was just that when I read this topic tonight and I was hoping that someone may have a solution, my app uploaded fine on two occasions to Apple but the latest seems to be stuck and without a solution my App is dead in the water 🙁
Hi Mobione team, I have managed to work out what the issue was in the uploading of my files, if you remember in my last issue I reported that I could not upload one Friday evening and the blame was addressed only to Android relating to Cordova 2.9, well I unchecked and went back to 2.2 and my file uploaded successfully to iTunes, can I ask that you investigate 2.9 as it seems that it still has flaws, I also posted in another thread relating to the same issue earlier today, perhaps the two can be linked as long as the other users get the success that I have today. finally I would like to express my gratitude to Kyle at Appstoreuploader for the time and effort he spent trying to get a fix, even during his vacation I would just like to say thank you for the support and look forward to using the service in the future>
Hi, just wondering if you managed to investigate the issue I raised in my last post with my concerns of Cordova 2.9, after 3 failed paid attempts and many more free tries by Kyle to resolve the issue, everything was pointing to something that I did wrong however I believe that after going back to 2.2 everything worked the way it should have in the first place. We all know that 2.9 had an issue a few weeks back and I have what I believe found a second issue, it’s important that no other user is left wondering what to do if the situation should arise again.
I gotta say, I’m confused by this whole thread. I use a very old version of the Application Uploader, on an equally old version of OS X. The _only_ issues I’ve ever had uploading an app to Apple have been 1. certificate issues 2. compilation issues caused by Mobione/Google Cloud services.
-1TC
1TC I encountered a problem that stopped my upload to Apple. I saw this tread which contained the same error message and hoped that someone could help me during this time no one at Mobione or Kyle at uploads could work out the issue, and it was thought that I was doing something wrong but after having six apps loading fine over the past year it was strange for an upload to fail, I changed from 2.9 to 2.2 and this fixed it however nobody has came back to confirm that their is a problem with 2.9
Hi mobione team, I have just read a post where you are asking someone to move up to Cordova 2.9, I know I was advised last week to do the same, my questions are
1) when and if do you plan to stop providing the option to use 2.2
2) it was 2.9 that would not allow my app to be accepted through the upload process as you can see in the topic,I will not be sending an update at the moment until the issue of pinch and zoom has been addressed but more importantly is the facility to upload to Apple, can you confirm what caused this action to happen and that it has been fixed.
>1) when and if do you plan to stop providing the option to use 2.2
MobiOne 2.5 is the last release with cordova 2.2.
>2) it was 2.9 that would not allow my app to be accepted through the upload process as you can see in the topic,I will not be sending an update at the moment until the issue of pinch and zoom has been addressed but more importantly is the facility to upload to Apple, can you confirm what caused this action to happen and that it has been fixed.
We are making cordova 2.9 the default version for the upcoming MobiOne 2.5. Internally it has priority and we test it first now for all potential issues including appstore uploads. The pinch/zoom regression you mention is caused by switching from the Cordova 2.2 childbrowser to the Cordova 2.9 InAppBrowser. Cordova 2.9+ implementations will use the InAppBrowser hereafter. The upcoming 2.5 milestone-3 to be released next week will enable pinch/zoom by default through the Designer’s GotoUrl action and the phoneui.showUrl() api.
Wayne, thank you again for the prompt reply, I will look forward to the next milestone, is there any new features or are they saved for the next official release
> I will look forward to the next milestone, is there any new features
1) 2.5 milestone-3 will introduce the concept known as a Target Design. This conceptual change is to better enable use of the new web editors in multiple contexts. The Target Design provides the context for all the app center tools. Formerly, the current Visual Design editor provided the implicit Target Design. The Target Design is analogous to the current project that some IDEs require to be set for their tools to work on.
2) also not totally new but use of the chrome devtools workspaces is being tested. We may be able to say more about that soon. The idea is with workspaces you can edit web files from with in the chrome devtools.
3) more improvements in the mobile web simulator
4) enable web editors to be used for any web development, not just mobione resource.
– I have been using mobione as my main web editor recently
