Problems in publishing App

Rhonan

Member
Licensed User
Longtime User
This is probably a newbie question, but I'm having problems successfully publishing my app on the google play store. I'll describe my problem and I hope you can help.

I've developed a simple app and through the debug mode I have tested it on various phones. all works well. I have created a private sign key and produced a release version... now i tried the google play store.

i uploaded the app, fixed all the minor issues, used the package name: eu.tooa.beta. All seemed well and google reports it as published. However nothing appears on the store or on the direct link that you can create.

I've tried different package names, no difference. says it is published, but nothing is available.

i produced a blank hello world using me.tooa.test1, and that worked, but a more complex programme did not.

PS: and before you ask.. i've waited 72 hours in some cases.. i've tried multiple times over last 2 weeks. ones that successfully published - one or two hours delay max.



This really has me scratching my head.. i can publish simple stuff, but not more complex programmes - even though google says they are published. Any ideas????
 
Last edited:

Peter Simpson

Expert
Licensed User
Longtime User
That's interesting.
In your Google Developers Console under 'Publishing options', it tells you how many devices your app is available on, what does it say?

Example below...

Supported Devices
[Learn More]
This application is only available to devices with these features, as defined in your application manifest.
Screen layouts: SMALL NORMAL LARGE XLARGE
Required device features
android.hardware.location
android.hardware.location.gps
android.hardware.location.network
android.hardware.touchscreen
android.hardware.wifi

This application is available to over 1488 devices.

Sent from my Nexus 7 using Tapatalk 2
 
Last edited:
Upvote 0

Rhonan

Member
Licensed User
Longtime User
it has me puzzled.. but thank you for all your comments.

1) my "hello world" apps are published near immediately so i doubt it's a backlog in the system

2) it says it's available to 1332 devices, i'm not asking for anything special other than it must be able to sms which i think knocks out a small number of devices

3) no difference in store options, no copy-protection

4) only difference in the versions is that i stripped out all the libraries i was using (s, stringutils2, phone 1.91, dialogs 2.80, http 1.20, httputils2, core 2.0)

I was wondering if there was an issue in the package name. i had read that there were some things you could not use in the package name (eg start with a number) but i can't find that page again. I'm attaching the manifest below.

PS: using ie9 as someone said browser may make a difference
PS: am using b4a 2.00, so i'll upgrade to 2.02 in case that makes a difference.

-------

<?xml version="1.0" encoding="utf-8"?>
<manifest
xmlns:android="http://schemas.android.com/apk/res/android"
package="me.tooa.tooa8"
android:versionCode="1"
android:versionName="v0.01"
android:installLocation="internalOnly">

<uses-sdk android:minSdkVersion="4" />
<supports-screens android:largeScreens="true"
android:normalScreens="true"
android:smallScreens="true"
android:anyDensity="true"/>
<uses-permission android:name="android.permission.READ_PHONE_STATE"/>
<uses-permission android:name="android.permission.SEND_SMS"/>
<application
android:icon="@drawable/icon"
android:label="TooA8">
<activity
android:windowSoftInputMode="stateHidden"
android:launchMode="singleTop"
android:name=".main"
android:label="TooA8"
android:screenOrientation="unspecified">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>

</activity>
</application>
</manifest>
 
Last edited:
Upvote 0

Rhonan

Member
Licensed User
Longtime User
just to update you guys... after a week a bunch of my test apps got published, including ones that i had subsequently de-published. I had emailed google support (they naturally did not get back to me) so maybe they did something.

So I think this needs to be put down to a flaky behaviour on google-play

thanks for all the comments.
R
 
Upvote 0
Top