Convert *.IPA to XCode project file

[Minh N Tran]

Hi

I have been searching for a way to convert *.IPA file to XCode project file for calabash test but got no clue. Could any one please give me an idea?

Thanks

Minh

[Saravanan Periyasamy]

As per my knowledge you can use iexplorer and copy the app files but not the secured or encrypted files. If its your own project you can get the project files and tweak it with the files and create your project path.

Again I am not an iOS delveoper to give the accurate answer

[Minh N Tran]

Thanks for the quick advise. Given i am a tester and my customer gives me only the IPA file to test his app. There should be a way to import that IPA to XCode and rebuild the app with calabash framework etc for testing i reckon

[Karl Krukow]

No, this isn't possible.

[Minh N Tran]

Thank Krukow for the confirmation. So given customers upload their *.IPA and *.APK files to lesspainful.com, can you please show me how you are going to use that IPA for the test? I am confused as that is not XCode project file.

Regards  

[kra Larivain]

You can't.

The app has to be built specifically with the calabash framework for it to work, which adds the code needed to automate the app.

This build is different than the build that is sent to apple, it's to be used only internally for automation purposes.

/kra

[Jennifer Liang]

This is where I am having hard time wrapped my head around the idea that the build I test is not the same build submitted to apple.  With continuous integration, isn't it ideal to "promote" the same build artifact through the pipeline until release?

[kra Larivain]

In a perfect world, it would be the exact same build.

The problem is that automating iOS apps requires adding an HTTP server to the app so your test scripts can communicate with the app. Without this piece, cucumber will be unable to talk to the app.

For that reason, you don't want to submit this build to apple: your users would have an open HTTP server accepting synthesized events on their phones, you can imagine what a bad person could do with this knowledge.

You are right that it somehow taints the app - but the changes are extremely unlikely to affect the regular build of the app - it's basically adding a few classes and the HTTP server that listens to incoming traffic.

As for the CI - just build two apps in your build tracks: the regular production app and the automatable version. When Automation signs off the automatable build, send the production app to apple.

/kra

--
You received this message because you are subscribed to the Google Groups "calabash-ios" group.
To unsubscribe from this group and stop receiving emails from it, send an email to calabash-ios...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.