Back to all discussions

  •   almost 12 years ago

App rejection (tester couldn't find the app after installation)

Hi,

I received my Gear app approval rejection with strange defect:

--- DEFECT TEST RESULT BEGIN ---

Application is not shown in Gear after installing it.
* Also, application is not shown in device's 'Gear Manager'.

1. Install Application
2. Check the screen

Application should be shown in Gear after installing it.

--- DEFECT TEST RESULT END ---

Did somebody have a deal with something similar?
My Gear app is a CLOCK widget with INTEGRATED type.
I tested it on the real device and there wasn't any installation problem.

Thanks,
Alexey

  • 12 comments

  •   •   almost 12 years ago

    On which device have you tested? What devices (resolutions) have you selected just before submitting to samsung apps?

  •   •   almost 12 years ago

    I had a similar problem when testing on Remote Test Lab. It wouldn't install on Gear and would show some errors in the phone log. The problem was that I didn't have this permission in my manifest file:
    <uses-permission android:name=
    "com.samsung.android.providers.context.permission.WRITE_USE_APP_FEATURE_SURVEY"/>

    I also added these because I read somewhere that they are recommended, but I think they didn't influence the installation on the Gear 2:
    <uses-permission android:name="com.samsung.WATCH_APP_TYPE.Integrated"/>
    <meta-data android:name="GearAppType" android:value="wgt"/>

  •   •   almost 12 years ago

    @andris -

    That WRITE_USE_APP_FEATURE_SURVEY permission requirement was the EXACT reason my app was rejected. Notice it was not included in the video that we got off the challengepost site: https://www.youtube.com/watch?v=VzoUeBS71jQ (AndroidManifest.xml shown at 29:00).

    But here it was in the rejection log:

    I am_crash: [3776,0,io.pendulum.pendulumHost,8961604,java.lang.SecurityException,com.samsung.android.providers.context.permission.WRITE_USE_APP_FEATURE_SURVEY permission is required.,NULL,-1]

    Another fun fact, I believe this error is only triggered on 4.4. My code with 4.3 ran fine, and I only found out recently that the run it the code 4.4 (note that the rules don't mention it and I only learned this from a post).

    So it left me a week behind schedule and hoping that was it for showstopping bugs.

  •   •   almost 12 years ago

    @Nate920, yep the video didn't have it. Also some documentation didn't have it. I was lucky enough to try and be able to run on Remote Test Lab, so I was able to fix it.

  •   •   almost 12 years ago

    @paulwedzik:
    I tested the app on Galaxy S4 Mini + Gear 2 Neo at home.
    And while submitting the app I selected all resolutions because my application Provider is an invisible service without activities.

  •   •   almost 12 years ago

    @andris:
    Ohh, I didn't have this permission too. I try to add it and test the application with and without that permission in Remote Test Lab.

    @Nate920:
    Are your rejection test case description was similar as mine?

  •   •   almost 12 years ago

    @kuelye :
    Don't think so, they couldn't install my app at all (so I was rejected for every one of those runs), and that permissioning error is in all the error logs.

    There's a chance they test on different phones in different orders and that is why we get different rejections. Maybe we have all new rejections to look forward to.

    The frustrating part is that we all followed their instructions and did nothing wrong. Our submissions are being bounced for reasons that were not in the documentation.

  •   •   almost 12 years ago

    @Nate920:
    Yep, It is not good that we are facing with this strange undocumented stuff.

    So, I check my app in RTL: it is installed with success on all devices, which I tested (Galaxy Note II with 4.1.1, Galaxy S4 with 4.2.2, Galaxy S4 with 4.4.2) WITHOUT any changes in package (I did not add WRITE_USE_APP_FEATURE_SURVEY and WATCH_APP_TYPE.Integrated).

    But I found out that If I try to...
    1a. hard reset my own Gear 2,
    1b. install my Clock Intergrated app through .apk on it
    ...then Gear Manager installs corretly only app Provider and output warning about app Consumer installation "Failed to install the app".

    And if I try to...
    2a. hard reset my Gear 2,
    2b. install my Clock Intergrated app WIDGET through Tizen IDE for Wearable,
    2c. remove this WIDGET
    2d. and install my Clock Intergrated app through .apk
    ...then Gear Manager installs correctly Provider and Consumer parts both without any warnings.

    Is it correct behavior and reproduced with anybody' intergrated app too?

  •   •   almost 12 years ago

    One of my app also failed because tester did not read the description, nor certification comments nor video from my testing and he/she was trying to take a photo by click on one of the icon rather then long tap on screen. Yes, it is ridiculous, but it is Korean style...

  •   •   over 11 years ago

    Hello everyone.
    Could someone guide m on the process of resending the application after rejection/fixing? What is the option on the Seller site to update the apk?

  •   •   over 11 years ago

    @kueyle:
    have you investigated this problem "Application is not shown in Gear after installing it."?
    In my case app visible on some devices and is not on others.

  •   •   over 11 years ago

    @paulwedzik:
    What devices does not display your app?
    I will check them.

    On this moment I check my app on Galaxy S4 Mini 4.2.2, Galaxy S4 4.2.2 and 4.4.2, Galaxy Note II 4.1.1 - and my app is visible on all these devices after installation.

Comments are closed.