Back to all discussions

  •   over 11 years ago

Passing Certification for Gear S

Has anyone managed to pass certification specifically for the Gear S?

I have an integrated app that works on the Gear S emulator and a Gear 2 real device, but certification failed for the Gear S stating the app can not connect. The same code path works fine on a Gear 2 during certification.

I've seen this issue reported on the Developer Forums as well, but no solution yet. Are there any specific config or manifest changes required for the Gear S? Or Accessory SDK version? Is seems the latest Accessory SDK has been recalled due to bugs, only the earlier 2.0.19 version is available on the website again. I had a look at the documentation, but did not see any required changes mentioned for SAP and Gear S.

Any help would be greatly appreciated (I've posted this on the Developer Forum as well, but this one seems to be frequented a bit more)

  • 14 comments

  •   •   over 11 years ago

    I havent done any changes to my tizen file or anything, except the version change in Tizen's config.xml file. It did pass the certification.

  •   •   over 11 years ago

    OK, so there is at least one data point :) You are also using an integrated app, can you tell me which version of the Accessory SDK you were using? And were you able to successfully connect to the emulator?

    You mentioned a version change in your config.xml. I assume you're talking about the widget version number and not the required_version="2.2" field in tizen:application tag?

  •   •   over 11 years ago

    yeah, widget version number, not the required version tag.
    Accessory SDK, as of now I am using the old one itself (after some comments/articles that it cant transfer more than 128 Bytes data, I was apprehensive about changing it). The accessory version number I dont remember exactly ( I just installed new Tizen SDK, and imported my old project into it and started editing :) ) . Hope it helps.

  •   •   over 11 years ago

    Can both sides of your apps communicate (between the phone and the Gear S emulator)?

  •   •   over 11 years ago

    I havent checked with gear S, but only with a actual Gear 2 Neo. So I just assumed it should work with Gear S too and it seems to be working.

  •   •   over 11 years ago

    In my case, the real phone and Gear S emulator and Gear 2 emulator communicates fine, no problems. Also, the phone and Gear 2 physical device communicates fine. I also assumed it should just work on a real Gear S, since I have no error conditions showing otherwise. But during certification, the host device doesn't communicate with Gear S. I am stumped, as I have no way to test on a real device and there are no Gear S devices yet on the Remote Testing Service.

  •   •   over 11 years ago

    Well, this is really unprofessional. They ask us to support the Gear S, and don't give us any clues on how to do that. We're shooting in the dark. After reading this, I guess I won't support the Gear S at all, at least that will increase the chance of passing the review. Losing a few points is still better than not even getting pass the test.

  •   •   over 11 years ago

    @codingcaveman: what do you have in the resource under:

    Is it TRANSPORT_WIFI or TRANSPORT_BT ?

  •   •   over 11 years ago

    While testing on the emulator I use TRANSPORT_WIFI (BT doesn't work for the emulators), but on the real device I change it to TRANSPORT_BT. WiFi isn't supported on the Gear 2, but I think it is on Gear S. I'm planning to add both transports for the next certification attempt to see if that makes any difference. Previously I've just used TRANSPORT_BT in the app submitted for certification.

  •   •   over 11 years ago

    If the Gear S fail to work, will Seller Office reject the whole app or only the Gear S version (and allowing Gear 2 version to pass) ?

  • Manager   •   over 11 years ago

    Hi Everyone,

    Thank you for your comments. I'm very sorry that you're having trouble. For instructions on how to use the Gear S emulator please reference the "Guideline on Testing Gear Applications using the Emulator" document (http://img-developer.samsung.com/contents/cmm/Guideline_on_Testing_Gear_applications_using_the_Emulator.pdf).

    If you have further questions about development or testing, please feel free to post them on the Samsung Developers Forum: http://developer.samsung.com/forum/en

    I do hope this is helpful!
    Serena

  • Manager   •   over 11 years ago

    Hi Everyone,

    Please note that, per today's update (http://gearappfinal.challengepost.com/updates/2150), The Remote Test Lab for Gear S is now open on the Samsung Developers site!

    The Remote Test Lab (http://developer.samsung.com/remotetestlab/rtlDeviceList.action) is a solution that enables developers to control devices remotely. Using the Remote Test Lab service, you can test your application on a real device through the web.

    For more information on the instructions, please refer to the upper right hand "RTL Help" on the RTL page.

    Best,
    Serena

  •   •   over 11 years ago

    They should have opened that remote test lab a long time ago so devs can fix the bugs. We only have 4 days left. I already submit the app without Gear S support since I have nothing to test. Good job, Samsung.

  •   •   over 11 years ago

    yeah i passed the certification. Samsung should provide more information for developers on gear s if they are pushing us to support it. We had to assume that the screen orientation is fixed at portrait view after watching a couples of youtube videos on Gear S...

Comments are closed.