Also all children will be taken in the flip as well.

In order for me to see your code, you have to wrap it in < code > block. If I can see it I can help troubleshoot it :)

Also if you don't define a replacement it will simply flip your panel and display nothing, which might be what you are seeing.


<replace type="flip" target="PANELALIAS" replacement="NAMEOFREPLACEPANEL" />


The replace action will trigger on whatever you are targeting, so if you have a specific panel you want to flip, then you need to add target="" and use either the path to the panel in question or the alias of the panel if you have given it one.

Any luck on getting your Apple certs working?

Well these things can be very particular. Without seeing your Apple Developer account, it could be something very minor. Generally though it is best practice to create your p12 with provisioning profiles for both ad-hoc and release all at once and upload it all to the studio. This helps make sure that they all line up correctly.

Given that you were able to create a p12 and provisioning profile once and submitted to Apple, I would probably suggest that you start the process over and generate a new p12 with provisioning profiles for both your Ad-Hoc and Release at the same time. Upload them all to the Studio in the appropriate places. Once the Ad-Hoc build is generated and tested (fixing this black screen issue), then you can generate your IPA for the new release build.

Alright, the first error you mention had to do with the error on our side.

The other error (failed_xcode_build) looks like something on your end. This means the system failed to build the xcode project with code signing - there could be a number of issues here. Generally this means you have a bad bundle identifier or a bad mobile provisioning profile.

Please make sure that you have presented your App Bundle ID in the studio correctly, this should be the Bundle ID search string and not the bundle seed ID.

See more info here: http://developer.apple.com/library/io...

Also make sure that the provisioning profile was built with the App ID that matches the distribution cert and the studio.

It looks like there is a small build error on our side based on a push we did last night. If you hover over the word "Failed" in the build logs, what error displays in the tool tip?

You should be able to reuse your .p12 for both provisioning profiles.

You need to make sure your .p12 was created using a distribution cert without a wildcard and that your provisioning profiles are associated with that same Cert. Have you seen the video we created to walk through this process?

The only difference between the ad-hoc and the release provisioning profiles is the one radio button setting it as ad-hoc.

You are certainly uploading them correctly, it must be the files are not lining up.

Unfortunately Apple doesn't make it easy on us do they? We have made it as easy as possible to use our system, if only Apple would simplify their process.

You will need to make very certain that the provisioning profile you are generating exactly matches the distribution certificate you used to create your p12. I most cases I suggest revoking and deleting your old provisioning profiles and creating a new one to ensure that it matches the cert you already have.

The portion you are doing in RareWire is correct, you can upload the same p12 as your cert, but the profile needs to be an ad-hoc that matches.