Samsung Wearable Tizen App Rejected No Deep Link

I submitted a new app to the Samsung Galaxy Store a week ago, and it got rejected. The Samsung wearable app is a companion app to an existing Android app. This Tizen app was built

Solution 1:

After scouring the entire internet, Samsung developer forums, Tizen.org, and every other place I could find, it turns out the advice on other SO answers is accurate, but incomplete.

For deep linking from a Tizen wearable companion app to an Android app, it's not enough to specify the master_app_playstore_deeplink - you must also specify the master_app_name, master_app_packagename, and master_app_min_version. The min version is the minimum versionCode of your Android app that is required for this version of the Tizen companion app to function.

In summary, you need all of these properties defined in the tizen-manifest.xml of your .NET Tizen companion app to deep link properly to its Android app:

<metadata key="master_app_name" value="MyApp" />
<metadata key="master_app_packagename" value="com.mycompany.myapp" />
<metadata key="master_app_min_version" value="620" />
<metadata key="master_app_playstore_deeplink" value="market://details?id=com.mycompany.myapp" />

If you do this properly, you can test the deep linking by uninstalling the Android app from your phone, then installing the Tizen app on your wearable. You should see a dialog like the following when you open the Tizen app, preventing you from using the Tizen app until you hit the OK button to install the Android app on your phone.

I've not seen this documented properly anywhere online, so hopefully this is helpful to someone else when their Tizen app gets rejected and they're not sure how to fix it.