App submission

Hello,

Please describe submission procedure step by step.

All I found is:

>>Prepare your app for submission:
Make sure your app manifest specifies all the products you wish to support.
Use the PkgTool to generate your .iq file. The PkgTool will make the binaries for all of the products you are supporting.
Your app is now ready to publish!

Could you explain how to sign app for submission?
Where can I take PkgTool, mentioned above?
  • In eclipse, select connectiq then export package application. That will create a .iq file. Then go to the app store and submit.
  • Thanks. This works for demo projects, but not for my own.

    "App eport failed: See console for details."

    console log is empty. Eclipse and SDK updated. Export folder exists and does not contain spaces/UTF-8 symbols in path.

    I guess I need to recreate manifest.xml.

    NB. 2Garmin. It is typo. "eport" should be changed to "export"
  • Quick question to Garmin.
    Why do you include in release file full path to project? Maybe somebody does not want to share this info?

    D:\<Private developer path>\Eclipse\C64Face\source\C64Face.mc

    I.e. create C64Face.iq, rename it to C64Face.iq.zip and enter the archive. Find inside 006-B1765-00\C64Face.prg and open it in Hex editor.
  • This should only appear in non-release builds of an app. We'll investigate why this is showing up in the release build. To make sure we're seeing the same thing, I'm only seeing the path one time. Are you only seeing it once in the PRG as well?
  • Thanks. This works for demo projects, but not for my own.

    "App eport failed: See console for details."

    console log is empty. Eclipse and SDK updated. Export folder exists and does not contain spaces/UTF-8 symbols in path.

    I guess I need to recreate manifest.xml.

    NB. 2Garmin. It is typo. "eport" should be changed to "export"


    That is a problem, it does say see console but nothing shows up in the console. Can we get that fixed next release?
  • This should only appear in non-release builds of an app. We'll investigate why this is showing up in the release build. To make sure we're seeing the same thing, I'm only seeing the path one time. Are you only seeing it once in the PRG as well?


    Yes, I see only one string inside the file.