Something similar happened to me a week ago. It's a trap for the unwary,
and they need a warning for it, and in fact I wrote to support suggesting
that, and they said they would look into it.
But it's no mystery what happened to you. There's a rule in Google Play
that once you have published
What you describe in #2 is what we see- target sdk 23, new build 47. Still
get same error listed in red. We may be able to promote to production
(havent tried yet) but that doesnt explain not being able to deactivate
build 42. Per #3, there are two sdk listed in beta (42 and 46) and cant
This has now been resolved. We continued testing on the alpha track. Once
we pushed an alpha build to production, we were able to disable both builds
stuck in beta without error. Definitely seems like some sort of bug on
Google side.
On Friday, March 18, 2016 at 1:18:22 AM UTC-4, Carl wrote:
>
So any ideas considering your suggestion to target sdk 23 doesnt work? Same
error, even with a build (46) that is targeting sdk 23?
On Thursday, March 17, 2016 at 8:48:35 AM UTC-4, Gameplay SmackDowns wrote:
>
> But target sdk IS set to 23 on new builds and it still will not allow me
> to.
>
>
In addition to our new builds targeting 23 (as you suggested), and still
getting the error - the error (in screenshot red) is referencing build 28,
even though build 28 is what is live in production and we are working in
the beta channel. We essentially have two builds now stuck in beta (46 and
But target sdk IS set to 23 on new builds and it still will not allow me to.
On Thursday, March 17, 2016 at 8:11:13 AM UTC-4, Carl wrote:
>
> Something similar happened to me a week ago. It's a trap for the unwary,
> and they need a warning for it, and in fact I wrote to support suggesting
>
I'm confused regarding what you are saying; we need to clarify:
1. When you say "targeting 23" are you referring to the targetSdkVersion in
the manifest, or are you referring to the project build target?
2. When you say that you have tried my suggestion, are you saying that you
have tried to
Anyone? Cant seem to get a response from Google Support.
On Tuesday, March 15, 2016 at 7:20:41 PM UTC-4, Gameplay SmackDowns wrote:
>
> In the Beta channel we were troubleshooting an apk issue. Current beta
> versions were being built in Android Studio, but to test we compiled and
> published
That is good to hear. I will make a note of it in case I encounter a
similar situation.
I wonder if this could be a way to get back to targetSdkVersion="22" after
releasing an APK in Beta with targetSdkVersion="23"?
On Fri, Mar 18, 2016 at 9:28 AM, Gameplay SmackDowns
9 matches
Mail list logo