I have a companion app which has been on market for a long time.
Now I submitted an update.
It got rejected because during review process they had issues during app installation.
Installation progress remains ongoing with never-ending “Installing” progress.
I don’t know whether they tried to reinstall or some other ways.
From their video I see that app has been installed ok on both sides, but the installation process itself cannot finish.
On RTL devices I can easily install both host and gear sides (separately).
Has anyone faced same behavior during installation process ?
Thanks.
Devices details:
phone: Galaxy S20 (SM-G980F), with Android 10 I guess
It was Gear S2 with Tizen 4.0.
My companion part of app (for gear side) has required_version=“2.3.2” in config.xml.
Can it be possible that Tizen 4.0 somehow is not backward-compatible with Tizen 2.3.2 ?
From certification rejection video it can be seen that app icon was added to both phone on gear sides.
Another point is that Customer Support refused to investigate this issue (because it is not related to Seller portal) …
It was Gear S2 with Tizen 4.0.
My companion part of app (for gear side) has required_version=“2.3.2” in config.xml.
Can it be possible that Tizen 4.0 somehow is not backward-compatible with Tizen 2.3.2 ?
If you built for any Tizen version newer than Tizen 2.3.2 then it is not compatible with Gear S2, You need to exclude it when you upload to the store. If you do want to include Gear S2 then you need to build a Tizen 2.3.2. Tizen 3, 4 and 5.5 are backwards compatible.
Another point is that Customer Support refused to investigate this issue (because it is not related to Seller portal) …
If you contacted Samsung Developer Program developer support they should have referred you to the seller portal support 1:1 Enquiry. They have all the information and should be of more assistance.
If you contacted Samsung product customer support they could not help but maybe they could have been more helpful.
See my next note on how to exclude Gear S2 devices
When you submit a round watch to the Galaxy Apps store you must select all watches 360 x 360 watches in a group to be tested. However, with Galaxy Watch Designer 1.7 or newer, S2 devices are not supported. This causes This causes a validation error you will get because they test on S2 device and it will not install. Here is what you need to do to rectify the problem.
Go to the “Binary” section of the “Add New Application” web page.
Upload your binaries as usual.
Next to the field “Add More Binary”, click on the number behind “Selected Device(s)”, which should read about 1766 or so.
A dialog window with a large list of hardware combinations shows up. Don’t get confused.
In the search field at the top right enter “Gear S2” - no need to press Enter.
The displayed list now only contains hardware combinations including the S2 watch.
Now uncheck the check box “Select all”.
Despite the message still reads 1766 devices selected", you have in fact deselected all S2 combinations, about 314+
9.Click the “Save” button at the bottom.
The dialog window closes and your device number(s) should now be lower
another update:
I have just retested wgt part in RTL (Galaxy Watch, Tizen 4.0.0).
It installs without any issue.
(widget itself cannot be tested in RTL because it requires host side app).
Thus I am fully confused on what was wrong during certification …
PS: can I send you apk/wgt to check from your side ?
For apps most Tizen Developers just designate Tizen 2.3.2 and build the older API as newer versions are backward compatible.
However, there are some API’s that require Tizen 3 or newer and now some may require Tizen 5.5 so they will have to be designated when you submit an app to the store.
Do you have any resources in your app, images or Fonts etc. those will often keep an app from installing.
Do you have any resources in your app, images or Fonts etc. ?
Those will often keep an app from installing.
Look, the wgt is fully same before and after I created app update with Samsung IAP onboard.
Only host side changed → it makes me think that gear side is ok but maybe IAP causing this or something else which is not under my control.
App uses SAP Accessory Framework (it is companion app after all), no unusual resources which you mentioned.
