This is my companion sdk…it’s about the Wear Os package sdk…companion is fine. I still got the warnings.
@mikich_blaz
No, this is something else. I am referring to accounts that were terminated due to malware.
Check here for the new requirements
1 Like
They are two different topics.
Creationcue is speaking regarding possible issues for App suspension and account termination.
You are referring to the new API target requirements from August, we are already talking about it here:
Please, let’s not create confusion within the threads.
Thanks!
2 Likes
One question … did you create your companion appying yourself or use the codes from the forum?
I created the companion app myself
1 Like
Yes I am aware of it…but don’t you think this is enough reason to reject only new uploads and to say it not safe:
“We’ve detected that your Wear OS app is targeting an old version of Android. To provide users with a safe and secure experience, Google Play requires all apps to meet target API level requirements”
That is a pre-compiled message that is sent every year when the API update deadline occurs.
The reasons for app suspension and account termination provided by Google refer to section 8.3 of the Developer Distribution Agreement regarding Behavior Transparency and other things that do not refer to the requirements and policies of the target API.
In those cases they only suspend the app or do not allow future updates but do not terminate the accounts.
Among other things, the notice of the new API target ends on August 31st, extendable to November 1st.
So, this is not the issue causing the accounts to be terminated as of today.
Which libraries are you importing in your companion app. Which permissions are you declaring in AndroidManifest.xml?
This is weird…
@Dadam, could you please check the minSDK of your rejected companion app?
@amoledwatchfaces `package com.creation.cue122watchface;
import androidx.appcompat.app.AppCompatActivity;
import androidx.wear.remote.interactions.RemoteActivityHelper;
import android.content.Intent;
import android.net.Uri;
import android.os.Bundle;
import android.os.Looper;
import android.view.Window;
import android.view.WindowManager;
import android.widget.Button;
import android.widget.Toast;
import com.google.android.gms.tasks.Task;
import com.google.android.gms.tasks.Tasks;
import com.google.android.gms.wearable.Node;
import com.google.android.gms.wearable.Wearable;
import java.util.List;
import java.util.concurrent.ExecutionException;
import java.util.concurrent.Executors;
public class MainActivity extends AppCompatActivity {
private RemoteActivityHelper remoteActivityHelper;
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
// Hide the app top bar
supportRequestWindowFeature(Window.FEATURE_NO_TITLE);
getWindow().setFlags(WindowManager.LayoutParams.FLAG_FULLSCREEN, WindowManager.LayoutParams.FLAG_FULLSCREEN);
setContentView(R.layout.activity_main);
Button installButton = findViewById(R.id.install_on_watch);
installButton.setOnClickListener(view -> launchPlayStoreOnWear());
Button infoButton = findViewById(R.id.installation_guide);
infoButton.setOnClickListener(v -> {
Intent intent = new Intent(Intent.ACTION_VIEW, Uri.parse("https://creationcue.space/how-to-install-your-watch-face/"));
startActivity(intent);
});
// Initialize RemoteActivityHelper
remoteActivityHelper = new RemoteActivityHelper(this, Executors.newSingleThreadExecutor());
}
private Node getConnectedNode() {
Node returnNode = null;
Task<List<Node>> wearableList = Wearable.getNodeClient(this).getConnectedNodes();
try {
List<Node> nodes = Tasks.await(wearableList);
for (Node node : nodes) {
if (node.isNearby()) {
returnNode = node;
}
}
} catch (ExecutionException | InterruptedException e) {
e.printStackTrace();
}
return returnNode;
}
private void launchPlayStoreOnWear() {
new Thread(() -> {
Looper.prepare();
if (getConnectedNode() != null) {
remoteActivityHelper.startRemoteActivity(
new Intent(Intent.ACTION_VIEW)
.setData(Uri.parse("market://details?id=" + getPackageName()))
.addCategory(Intent.CATEGORY_BROWSABLE)
);
Toast.makeText(this, "Please check your watch", Toast.LENGTH_LONG).show();
} else {
Toast.makeText(this, "Watch is connected to mobile", Toast.LENGTH_LONG).show();
}
}).start();
}
}`
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:tools="http://schemas.android.com/tools">
<application
android:allowBackup="true"
android:icon="@mipmap/ic_launcher"
android:label="@string/app_name"
android:roundIcon="@mipmap/ic_launcher_round"
android:supportsRtl="true"
android:theme="@style/Theme.CC005">
<activity
android:name="com.creation.cue122watchface.MainActivity"
android:exported="true"
tools:ignore="LockedOrientationActivity">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
</application>
</manifest>
1 Like
@amoledwatchfaces
Just rising the minSDK from 26 to 27 cleared the “Trojan/Smsspy!” so it cant be the code…or not?
Which app you are using for scanning AAB file for viruses ?
Avoid using “background” keyword on your description, you can change it to “styles”
2 Likes
Is there a “no-no” list floating around of terms that should be not used or avoided in descriptions? That aside, that wouldn’t be grounds for account termination would it?
I have used this companion app source code shared by Bredlix here and
-
I Updated around 30 watchfaces with new companion app with no rejections. in last 2 months.
-
The Android Studio Version i was using since 2021 to 2022 Called Android Studio Electric Eel.I had problems some errors with Gradle Plugin .
-
So i installed Android Studio Version Latest in May Called Android Studio Jelly Fish. And the companion app had no SDK lower version errors. The companion app then generated successfully.
-
The watchface studio version i used to update was 1.6.9.
-
Just checked there is a New Android Studio Version available after it called Koala.
Stable Releases.
a. Android Studio Giraffe. (After Electric Eel)
b. Android Studio Flamingo
c Andorid Studio Hedge Hog
d. Android Studio Iguana.
e. Andorid Studio Jelly Fish ( i used this one)
f. Android Studio Koala (Latest Stable).
very important point to note is that After electric eel . when i installed Jelly fish release. It was installed separately on my windows 10 PC. The previous Android Studio i had Electric Eel was not over written.
Now Electric Heel Android studio version behaved differently with Companion app there were many error like lower SDK and compilation errors.
i didnot have any issue with Bredlix Companion App shared here and i managed to get 30 times older watchfaces with this new companion app.
The companion app was compiled by me was made
in Android Studio Jelly fish. It has 1 link to watchface review posting and a 2nd to my Google Playstore Developer link. It has no redirects to own website blog or page outside of playstore.
I am going to install the Android Studio Jan Stable Koala release . But since The watchface studio 1.9.6 version also now needs to be updated. I will test updating companion app re generated with latesf Android Studio Koala release Jan 24. when this WFS issue is resolved.
I am sharing this info with you to let you know so if this can help in anyway.
link
1 Like
minSdk = 24
targetSdk = 33
@usadesignwatchface
For scanning the app you can use https://metadefender.opswat.com/ or https://www.virustotal.com/
p.s. I have no issues or warnings from google (…yet), my account is live. I just published a new watch face yesterday with no problems (except that we have to update all watch faces till 31/08 so we have to wait for the new WFS that targets API33)
No problems found in my companion app
1 Like
Thanks for your sharing info.
Omg. My company app scan detect Trojan
I try increase minSdk also same problem.
I try build empty activity .aab file also I detect Trojan-Spy!!.
My system:
MacBook Pro Ventura 13.2.1
Android Studio Jellyfish 2023.3.1 Patch 1.
Android Studio Koala Feature Drop 2024.1.2 Canary 2.
(I install this Koala bcoz I would like to learn Wear OS 5 sample code)
My test,
If I use Android Studio Jellyfish to build empty activity .aab file - > Trojan detected
(All my companion app is using Jellyfish)
If I use Android Studio Koala to build empty activity .aab file - > No issue found.
I scan MacBook with CleanMyMac x no issue found.
Is my MacBook got virus? I am not good about virus/ trojan.
I don’t know why my android studio jelly fish generated file detect trojan. Is it very serious harm to user? I am very very sorry, I really not intended this to happen.
Anyone good in Android Studio please?, I would like to study/ know why my android study jelly fish generated .aab detect trojan. Anyone can kindly help or give some guide please? What is the root cause of this?
Thank you very much in advanced!
Reading all the experience here is scary!. I have been living in a happy bubble with Google play making small apps and watch faces having no idea google is so ruthless.
My wild guess is, I noticed, those who got their app suspended for “malware, behavior bla bla” reason, they are using WFS beta version. I am still using the 1.4.2 the last stable version Samsung created way back in 2023, never had any issue until now with the API 34 requirement. It is possible that there are some issues with the beta version that is causing this error and getting all the accounts suspended. but its just my wide guess.
Also from developing apps, I can tell you google DOES NOT like external links or files being downloaded from outside in your apps. specially if link is not from an https. even with https they dont like external links. Safe way for external links is to eg. open the app, like play store, directly rather than giving it a raw url going to browser then app store.
I find it sad that there are no moderators from Samsung here. 
5 Likes