With the only version that I can use on the Play Store without removing customizations and features from my Watch faces downloaded thousands of times for some time:
WFS 1.3.13
HI @r.liechty_SDR ,
That message does not come from the review team.
It’s a warning that has appeared on several watch faces since September 5th on Play Console.
From my point of view, it appeared after the release of Wear OS 4.0
The WFS version does not matter. It happens with both WFS 1.3.x and 1.5.x
@Matteo_Dini
Are you sure that it happens with 1.3.13? Your watch faces made with 1.3.13 are still appearing at the top paid list. My watch face made with 1.5.X was removed from the list in the watch face category.
The warning says: This means it will likely be less visible on Google Play, and users may see notifications in your store listing. We recommend resolving these issues as a priority.
What I can tell you is that my watch faces were created with WFS 1.3.x and I also see that message on Play Console.
here are some details from the crashes page. I hope it can help you to understand the problem. As you can realize just Samsung watches have crashed. However, all devices are included on the device catalog page.
Exception java.lang.NullPointerException: Attempt to read from field ‘r5.k com.samsung.android.wearable.watchfacestudio.a.y’ on a null object reference
at com.samsung.android.wearable.watchfacestudio.WatchFaceStudioRuntime.onConfigurationChanged
at android.app.ActivityThread.performConfigurationChanged (ActivityThread.java:5654)
at android.app.ActivityThread.handleConfigurationChanged (ActivityThread.java:5859)
at android.app.ActivityThread.handleConfigurationChanged (ActivityThread.java:5775)
at android.app.servertransaction.ConfigurationChangeItem.execute (ConfigurationChangeItem.java:42)
at android.app.servertransaction.TransactionExecutor.executeCallbacks (TransactionExecutor.java:135)
at android.app.servertransaction.TransactionExecutor.execute (TransactionExecutor.java:95)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:2073)
at android.os.Handler.dispatchMessage (Handler.java:106)
at android.os.Looper.loop (Looper.java:246)
at android.app.ActivityThread.main (ActivityThread.java:7690)
at java.lang.reflect.Method.invoke
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:593)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:995)
Exception java.lang.IllegalStateException: The specified child already has a parent. You must call removeView() on the child’s parent first.
at android.view.ViewGroup.addViewInner (ViewGroup.java:5272)
at android.view.ViewGroup.addView (ViewGroup.java:5101)
at android.view.ViewGroup.addView (ViewGroup.java:5041)
at android.view.ViewGroup.addView (ViewGroup.java:5013)
at com.samsung.android.wearable.watchfacestudio.editor.e.accept
at java.util.ArrayList.forEach (ArrayList.java:1262)
at androidx.viewpager2.adapter.FragmentStateAdapter.f
at androidx.recyclerview.widget.RecyclerView$s.i
at androidx.recyclerview.widget.m.c
at androidx.recyclerview.widget.m.b
at androidx.recyclerview.widget.m.run
at android.os.Handler.handleCallback (Handler.java:938)
at android.os.Handler.dispatchMessage (Handler.java:99)
at android.os.Looper.loop (Looper.java:246)
at android.app.ActivityThread.main (ActivityThread.java:7690)
at java.lang.reflect.Method.invoke
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:593)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:995)
Exception java.lang.IllegalStateException: The specified child already has a parent. You must call removeView() on the child’s parent first.
at android.view.ViewGroup.addViewInner (ViewGroup.java:5272)
at android.view.ViewGroup.addView (ViewGroup.java:5101)
at android.view.ViewGroup.addView (ViewGroup.java:5041)
at android.view.ViewGroup.addView (ViewGroup.java:5013)
at com.samsung.android.wearable.watchfacestudio.editor.e.accept
at java.util.ArrayList.forEach (ArrayList.java:1262)
at androidx.viewpager2.adapter.FragmentStateAdapter.f
at androidx.recyclerview.widget.RecyclerView$s.i
at androidx.recyclerview.widget.LinearLayoutManager$c.b
at androidx.recyclerview.widget.LinearLayoutManager.Y0
at androidx.recyclerview.widget.LinearLayoutManager.L0
at androidx.recyclerview.widget.LinearLayoutManager.d1
at androidx.recyclerview.widget.LinearLayoutManager.q0
at androidx.recyclerview.widget.RecyclerView.Y
at androidx.recyclerview.widget.RecyclerView$w.b
at androidx.recyclerview.widget.RecyclerView$z.run
at android.view.Choreographer$CallbackRecord.run (Choreographer.java:998)
at android.view.Choreographer.doCallbacks (Choreographer.java:796)
at android.view.Choreographer.doFrame (Choreographer.java:727)
at android.view.Choreographer$FrameDisplayEventReceiver.run (Choreographer.java:983)
at android.os.Handler.handleCallback (Handler.java:938)
at android.os.Handler.dispatchMessage (Handler.java:99)
at android.os.Looper.loop (Looper.java:246)
at android.app.ActivityThread.main (ActivityThread.java:7690)
at java.lang.reflect.Method.invoke
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:593)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:995)
Sorry for too much messaging.
Lately, I’ve been getting reviews like this. If 'ı’m posting to wrong topic sorry.
Can you send that report as a Developer Support Request It looks like it may be a watch face studio error to me.
Ron
Samsung Developer Relations
Did these start last week?
I looked and there was an Androidx library Update last week and I wonder if that is the issue.
And one on September 6 as well.
Ron
In my case, as I wrote in the previous comments, since September 5th.
If i am right rating and reviews are country based.
2 Likes
I have many designs. How can you know which one I’m talking about?
@r.liechty_SDP
September 6 for all of my designs.
This is completely unrelated to this topic, for which I apologize, but it looks like some clarification is needed to get things back on track.
Visibility of ratings and reviews is based on multiple factors. Users can’t see all reviews, only the app dev can.
This is because Play Store changed how reviews work relatively recently (beginning of this year I believe), in a way that users can only see reviews from other users who are in the same region, and who are using the same/similar device models.
For example, if most reviews are from users based in the US (as this is usually the largest market), other users from EU won’t be able to see any of those reviews.
Therefore, you can’t use this as an argument - it makes no sense.
If you don’t see any reviews, it just means there weren’t any users from within your region, who also happen to be using similar device models as you are.
3 Likes
Sorry if i want off track will delete my replies…noted on your point
I know for a fact in the Galaxy Store and I believe in most online stores including Play Store
Reviews are only shown in the country of the reviewer. So buyers in the US never see any reviews from someone in England or Singapore even if they are in English.
Ratings are the same way.
Ron
2 Likes
Today I got this notification. By this way, I wanted to ask again. Is there any update/determination to solve this issue? @r.liechty_SDR
Changes to the definition of user-perceived crash rate for Wear OS apps on smartwatches
30 Sept 2023 03:46
We’ve made changes to the definition of user-perceived crash rate for Wear OS apps on smartwatches. For Wear OS apps on smartwatches, user-perceived crash rate will now include both foreground and background crashes. Smartwatches always have watch faces running in the background, and Wear OS apps are often relegated to the background deliberately by users, even during active usage, due to the small screen size. This change means that user-perceived crash rate for Wear OS apps now more accurately reflects what users are experiencing, making it easier for you to act on.
This is (another) issue that we cannot fix on our own.
It sounds like a watch face format issue and possibly @amoledwatchfaces may have a handle on this I tagged him.
Of course I blame this on Google Play Services I think it reports on your watch face incorrectly
Ron
Samsung Developer Relations
1 Like
@amoledwatchfaces I would be grateful if you could share your opinion with us.