You create an Ad-Hoc build by navigating to the build section and creating an IPA using an Ad-Hoc provisioning profile and your existing p12 file. Make sure you add your device UDID to the provisioning profile.

I would start by changing your wire version to 1.2 and then test by installing an Ad-Hoc build. If that doesn't fix the issue let me know and we can try a few other things.

We are about 80% complete with our build. We anticipate releasing officially later this year after we have a short round of testing.

Lets try and get to the bottom of this.

Did you create this App as a universal App in your studio settings?

Are you using platform tags? We have seen this issue with an incorrect platform tag before.

I am assuming you created and tested with an Ad-Hoc build before you submitted this?

Great to hear! Let me know if you need any more help.

You will go through the same process for a store build, only you create a provisioning profile that matches your p12 for a build not adhoc. These you will upload at the bottom of the Apps setting page rather than the Ad-Hoc page.

IPAs should display in the Build Log, what you are seeing is version history for the App project. Anytime you attempt to make a build either from the Ad-Hoc section or the Publish button it will show up in Version History.

It is very important that you create you p12 correctly, it can be used for both adhoc and build, but your provisioning profiles are unique and have to match with the distribution cert you made your p12 file with.

I am not seeing the code. Try adding < code > blocks around the example.

Usually that error means that you have opened a line of code with a different name than it was closed with.

Are you looking at the tutorial on twitter? http://content.rarewire.com/wordpress...

In order to retrieve an IPA file, you must follow the steps to set up an Apple Developer Account. Once that is complete, you will need to create a distribution provisioning profile as well as a distribution certificate which you will use to make a .p12 file that will contain your cert and a private key.

Here is a short video on how this is done: https://vimeo.com/41295380

Once you upload the p12 and your provisioning profile to the studio, then you will be able to make IPA builds. Upon a successful build, you will be taken to the Build Logs tab and the build will be available for download directly from the studio.

Live Updates are a good way to push content to your App instantly, making a build with this option will not produce an IPA, but will send the update through the CMS. You are still required to have your certs set-up though.

Currently in Beta a live update is free, but once we come out of beta it will be part of the $250/month plan.

It looks like it is not likely that we will support midi at this time. It is not natively supported in webkit, so it would require some work to develop a plugin that works well with our engine.

At this time I would suggest converting your midi files to mp3, they should remain lightweight comparatively.

I went ahead and logged a support ticket for this request, so maybe it will gain some traction down the road.

Thanks for the question!
Ian

Let me poke around about that tomorrow and I will let you know!

The sound action tag only supports the following audio types: mp3, mp4, wav, aiff, aac