I'm ready to publish my app developed with Icenium which is going to replace an old app already published in the Apple App Store (developed with something else). I'm facing the following problem; 

The previous published app ID contains a "-" in the ID, for example: "com.mycompany.my-app"

I need to replace that app with the new version but Icenium graphite is not accepting the "-" in the application identifier, it keeps saying that "the app identifier must contain at least three alphanumeric string separated by a dot, the alphanumeric strings must start with a letter" if I remove the "-" the error disappears but then the ID never matches with the ID in the provision file.

Any ideas?

Hello Daniel,

The validation logic for the app identifier in Icenium is created to handle the requirements for both Android and iOS platforms. That along with the upcoming support for WP8 platform support, forced us to "consolidate it" so that it is valid for all platforms. I believe dash is invalid character for App id in Android - thus the error.  In cases like yours when you already have published an app with valid App ID for a platform and need to maintain it, you can manually edit (see Edit Configuration Files) the Info.plist and hardcode your old app ID i.e. you should replace <string>$AppIdentifier$</string> with <string>com.mycompany.my-app</string>.

Regards,
Steve
Telerik
You've missed the Icenium Visual Studio Integration keynote? It has been recorded and posted here.
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.

Thank you Steve, I tried the suggestion and I was able to manually edit the info.plist file and hardcode the old application ID, however when I try to publish to the Apple App Store  I'm still seeing the same error about the bundle identifier in the provision does not match the app ID and in fact it does not because the project properties still shows the ID without the dash ("-").,

Do I need to change something else to make this work?

Hi Daniel,

Yes, sorry for omitting that part. You would also need to edit manually the .proj file of your app to contain the problematic AppID since this is the only way to avoid our validation logic. You can push your app in a github repo and there you would see the .proj file for it. Edit the <AppIdentifier></AppIdentifier> section to contain the desired AppID i.e.

<AppIdentifier>com.mycompany.my-app</AppIdentifier>

This way the build button would be enabled and you would be able to build successfully. We apologize for the temporary inconvenience, we would think of a better way to handle this for the upcoming version of Icenium.

Regards,
Steve
Telerik
You've missed the Icenium Visual Studio Integration keynote? It has been recorded and posted here.
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.

Thank you Steve!

That worked

nevermind, it seems to be working

Hi, Steve!

What configuration for Android apps? When I change the manifest package to "package='mypackageoriginalname'" the icenium Build and Deply an error app to my Android Device. When start app, shows a message: "'APP' Stops" and close.

Hello Andre,

I was able to successfully build an Android app with your App ID "com.liv***********sta" and install and run it successfully on a couple of Android devices - no errors whatsoever. Just to be sure we're on the same page, you need to make two changes before using the Publish option in Mist/Graphite:

• change the App ID in the .proj file of your project, it should become: <AppIdentifier>com.liv***********sta</AppIdentifier>
• change the App ID in the AndroidManifest.xml file, it should become:
  
  <?xml version="1.0" encoding="utf-8"?>

  <manifest android:versionCode="$AndroidVersionCode$"   

                      android:versionName="$BundleVersion$"

                      package="com.liv***********sta"

Now you're ready to build your app for publishing on Google Play Store.

If your app force closes, there must be a different problem unrelated to the signing of the app. You can build it in Debug mode and try to figure out the reason by inspecting the logcat.

Regards,
Steve
Telerik
You've missed the Icenium Visual Studio Integration keynote? It has been recorded and posted here.
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.