•   over 11 years ago

Help Regarding App Updation - Integrated Gear App

My case is of a integrated app. What all changes are needed to be done to all the manifest files and config.xml files and anything else also if needed for it act as a update to the older application ? As of now if I install my binary on gear its acting as a new app (without even deleting the old one). Can anyone please help ..

  • 26 comments

  •   •   over 11 years ago

    The only changes I made to config.xml was to change the version string. In my host app manifest I changed the versionCode and versionName. Updates work as expected.

    I've not tested any of the following, but I can imagine that updates or installs won't work properly if:
    1. You changed the signing certificate of the Gear app
    2. You change the signing key of your host app (or mix and match between debug and release keys, e.g. if your Gear certificate was generated with a debug key, but your host app is signed with a release key)
    3. You change the application id or package in confix.xml
    4. You change the app type, i.e. integrated, standalone, etc.

    As I said, it is just conjecture - I've not tested any of the above, I'm just throwing some ideas out there to investigate.

  •   •   over 11 years ago

    codingcaveman, got a weirder problem. Now Some days back I got mail from samsung sayign change your gear ID because its clashing with some others(mostly because you have used demo projects ID itself). So a week back I changed the package ID and uploaded the new file. It got accepted through registration and is for sale. Now when I am trying to uplaod its saying "Package ID (wgt) is not valid. Package ID (wgt) of registered binaries must be the same.". Any idea what to do? Should I go back to my old demo proejcts project ID or something?

  •   •   over 11 years ago

    That is probably the reason why the updates don't work then. I think the package id is what Tizen uses to uniquely identify an app, e.g. you can do 'sdb uninstall _package id_' to uninstall an app via the IDE command terminal. Two apps with the same package id would probably not be able to install on the same device, which is why Samsung would have asked you to change it.

    I'm not sure what you should do, though. Maybe uninstall all apps on your device and download your current app from the Samsung store. Once installed, try and find the package id for your installed app, it would be on the device file system in /opt/usr/apps/package_id

    Then make sure you upload your new binary with the same package id. If it is a shared demo one, then you may have problems with it playing nicely with other apps, though. The best solution would probably be to completely republish apps with shared package ids, and replace them with new ones. But I don't think you can do that for the competition. Did you fail certification with the shared id?

  •   •   over 11 years ago

    When I edited my package name and submitted it a week ago, it passed the certification. Only now all the trouble started. Thanks for the suggestion. Trying to do that.

  •   •   over 11 years ago

    The ID with which I uploaded the app now, and the id of my app downloaded from Galaxy Apps, both are same. Just tried and still failing. Dunno what to do with Deadline just around the corner :(

    PS : Mailed the challenge Post People. Hope they see it in time to do something about it. do you know how to contact stefgreat (Moderator)?

  •   •   over 11 years ago

    No, sorry, I'm just a another dev, I don't know how to contact the moderators apart from through this forum. One last thing I thought of was to check that your package id and application id has the same value, e.g. package="rTWs4TW3sw4" and application id = "rTWs4TW3sw4.YourAppName". Good luck!

  •   •   over 11 years ago

    I'm facing similar issue, last week I submitted an update to my app which got rejected as it had some issues. Now I fixed those issues and I'm sure that I've not touched manifest or config.xml still it says "Package ID (wgt) is not valid. Package ID (wgt) of registered binaries must be the same."

    @chakri1vr1 exactly same issue, I've check package id in /opt/usr/app and it matches the one I've uploaded.

    No idea what to do now.

  •   •   over 11 years ago

    Exact same issue :(

    I've even double checked old and new config.xml in wgt and in both is exactly the same line:

    And I don't have an idea what to do....

    Error "Package ID (wgt) is not valid. Package ID (wgt) of registered binaries must be the same." is simply NOT TRUE.

    Something really is not working as it should...

  • Manager   •   over 11 years ago

    Hi Everyone,

    Thank you for posting about this issue. I'm very sorry that you're having trouble! We've documented your issue and shared it with the Samsung team for investigation. We hope to have a solution for you very soon.

    In the mean time, please contact the Samsung Certification team directly by doing one or both of the following:

    A) Contact the Seller Office (http://help.content.samsung.com/csseller/main/main.do)

    B) Leave a message about app operations or bug fixing in the “Message to Certification Team” field when registering your app on Samsung Apps.

    I’m sorry I couldn’t be of more help and we'll try to get this sorted out for you as soon as we can.

    All the best,
    Stefanie

  •   •   over 11 years ago

    Dear Stefanie,
    I have already raised the same issue at Seller Office support forum. It generally takes around two days for them to reply which at this point is not going to help us unfortunately. And we cant leave any message to certification team because the app itself wont get submitted first hand. Hope they fix it quickly.

    Regards,
    Chakradhar

  •   •   over 11 years ago

    Dear Stefanie,

    Any update regarding the above issue? We are nearing the deadline and its just 4 more hours to go. Any reply from Samsung or your ( Challengepost's ) side regarding this?
    Regards,
    Shubhra

  • Manager   •   over 11 years ago

    Hi ssp_SRIB,

    Thanks for your note. I'm sorry, but we do not have a resolution from the Seller Office yet. Please know that we are taking this very seriously and we will update everyone as soon as possible.

    Best,
    Serena

  •   •   over 11 years ago

    I'm having the same issue. That's really annoying.

  •   •   over 11 years ago

    what if this issue is not resolved before submission deadline?

  •   •   over 11 years ago

    Are there any official resolution on comment on this issue?

  •   •   over 11 years ago

    I guess since its last minute those reporting the issue are getting 1 on 1 assistance...
    Since only ~200 submissions are there most of the teams already submitted before, last week itself submission of an "update" to our app was okay, but when we did incremental changes and tried our final submission we are facing this issue.So i would suggest you to mail Seller Office (lodge an enquiry) as well as challengepost support (we did the same and have received their respective responses,but still issue is not resolved though and still we are puzzled about the fate of our submission) but since we reported the issue before the deadline we are hoping to be considered.The higher the number of issues reported, the faster it should be resolved and considered as a serious issue, i suppose.Only concern I have was the issue created during first round submission trouble
    Hope it helped.We are consoling ourselves with the same.
    Regards,
    Shubhra

  •   •   over 11 years ago

    you have 2 weeks to get it though certification
    which in real terms means 7 days and then allow 7 more for it to get though again
    which basically means one fail (maybe 2)

  •   •   over 11 years ago

    I am experiencing the same, or perhaps different problems.
    My update made it through Device test and was rejected afterward because I did not include the master APK, despite the fact that there is *no place to include it*

    I would have loved to modify that update, but it didn't let me do that - I had to delete, so starting over on all the description and screenshots and everything.

    By the way, in which line of config.xml is this package id that you are talking about?

    For example, in this snippet, I see two places that say id= and one place that says package= and no place that says packageId=.

  •   •   over 11 years ago

    CUSTOMER SUPPORT REPLY FROM SAMSUNG SELLER OFFICE:

    "Here is the answer to your enquiry.
    Dear Customer,

    Thank you for contacting us. We appreciate the opportunity to assist you.

    Regarding your inquiry, we would like to inform you that there is an error in Seller Office when changing a binary file.
    And the error will be resolved on October 6th, so please update the application after that.

    We are sincerely sorry for the inconvenience in using our services. Your kind understanding and continued support is very much appreciated."

    Finally some relief!!

  •   •   over 11 years ago

    Just got the same.

    Hmmmmmmmmmm.......
    Anyone knows, when those mentioned "Korean holidays" fall?

  •   •   over 11 years ago

    NathanWA , you must be having this line in your code. This package is what everyone is referring to as Package ID, and id is just a concatenantion of your package and your application name.
    tizen:application id="R5GkGwwnP5.SimpLog" package="R5GkGwwnP5" required_version="1.0"

    PS : Thank god we received the mail confirmation from Samsung that the fault is on their side. Now that we are sure of that, Serena/Stefanie , is there going to be any change in the schedule for apps to get certified? or is it the same 13th of October?

    Regards,
    Chakradhar

  •   •   over 11 years ago

    dunqan, what mentioned "Korean Holidays"? Where is it mentioned?

  •   •   over 11 years ago

    Google search shows holidays on October 1, 3, and 9.

    http://www.timeanddate.com/holidays/south-korea/

  •   •   over 11 years ago

    Dear Stefanie or Serena, and all other participants of this great contest !

    I have very similar problem. Please take a look at the replay from Premium Solution Support:
    http://i.imgur.com/Dm0Gfal.png

    My application has been certified successfully already, but I just wanted to add some features I mentioned in my promotional video, but I can't do it because Seller Office has the bug mentioned in the above link.

    I have already lost because of that like 5 days. This is real problem. Please could you advise if we can have more time for certification if we proof that the problems relay on the Seller Office side ?

    I have just gave clear evidence we are ready but Seller Office has problems and we can't proceed according to the rules.

    Thank you for your replay !

Comments are closed.