Publishing B4A app problem

[wdegler]

In trying to upload my .apk file to Market for publishing on Developer Console, I get the message
"Market requires versionName to be set in AndroidManifest.xml".

I used B4A to create the app and put that information in the manifest file and I see that it is there.

I used the browse button again to indicate the (default) location of the manifest file. I then got the self-contradictory message
"The file is invalid. ERROR. dump failed because no AndroidManifest.xml was found".

The second line of my manifest file is
"-<manifest android:installLocation="internalOnly" android:versionName="DrillMathFacts1" android:versionCode="1" package="WDD.DrillMathFacts".

"I successfully published an app before now in the same way; it worked!
Comparing the two manifest files, I see that this one IS valid.
How can I publish this app?

 

[Erel]

Try publishing it with a different browser. It sometimes solves issues related to the market.

 

[wdegler]

Following your suggestion...

Thank you for your suggestion. I have now tried publishing my app using Internet Explorer, Chrome and FireFox. I have also tried using a different computer. I remain unsuccessful. The Manifest.xml file created by B4A which is not being accepted is

<?xml version="1.0" encoding="UTF-8"?>
-<manifest android:installLocation="internalOnly" android:versionName="DrillMathFacts1" android:versionCode="1" package="WDD.DrillMathFacts" xmlns:android="http://schemas.android.com/apk/res/android"> <uses-sdk android:minSdkVersion="4"/> <supports-screens android:anyDensity="true" android:smallScreens="true" android:normalScreens="true" android:largeScreens="true"/> -<application android:label="Drill Math Facts" android:icon="@drawable/icon"> -<activity android:label="Drill Math Facts" android:screenOrientation="unspecified" android:name=".main" android:launchMode="singleTop" android:windowSoftInputMode="stateHidden"> -<intent-filter> <action android:name="android.intent.action.MAIN"/> <category android:name="android.intent.category.LAUNCHER"/> </intent-filter> </activity> </application> <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/> </manifest>

I would appreciate any other help you can provide. The app itself works well on both the B4A emulator and my Android 2.2 Samsung 4G Galaxy S phone.

 

[Erel]

Can you zip the file and upload it?
Are you using the default manifest, or is it a custom one?

 

[wdegler]

Requested zipped file attached

This is not a custom manifest file, just the standard one with my defaults.
I have attached the zipped AndroidManifest.xml file.

 

[Erel]

Your file looks fine.
Did you remember to sign the apk file as described here: Signing your application before uploading to Android market

Also try to change the versionCode and VersionName and see if it helps.

 

[wdegler]

Following your suggestions...

I renamed the version name to "1.1".

Apparently, I DID forget to sign the file. I see a KEYSTORE file in the folder from my first (successfully) published app but do not know how it was created.

I copied that file to my present app folder (renaming it accordingly) to use as this present app's KEYSTORE file. Now, trying again to publish the app, the .apk file upload attempt produces the same error message as before: "Market requires a Version Name".

Any further suggestions will be greatly appreciated. At the present time, I am unable to publish anything to market.

 

[Erel]

You are probably signing with the debug key. You should create a new key. Note that you will not be able to update your previous app if you have lost this key.

 

[wdegler]

My present status

I have successfully created a new private key.

I am convinced that my present status is as follows:
1. I have a good apk file.
2. I have a good AndroidManifest.xml file (with version name and code).
3. I have a good KEYSTORE file (with a new key).

Everything seems to match my previous successfully published app.

When I click "Upload" for my apk file, the following message appears in red:
"Market requires versionName to be set in AndroidManifest.xml."

Is there anybody else having this problem?

 

[Kamac]

I did have it too, but i opened up AndroidManifest.xml and on this line:

      android:versionName=" "

i typed

      android:versionName="Mighty version"

then, i made AndroidManifest read-only and compiled

 

[wdegler]

Thanks for all of your responses. Possible solution...

I have a theory as to my problem which I am pursuing to a likely solution. My AndroidManifest.xml file MAY be going into a different apk. Will let you know.

 

[wdegler]

Success!

I have successfully published this second app!

The problem was that B4A was creating my apk file under the name result.apk rather than the named apk I already had. I don't know why this naming happened but I submitted result.apk and all else worked!
Problem solved.

Thank you Erel for your patience!

 

[agraham]

I don't know why this naming happened

From Erel in another post.

The name of the APK should be the same as your main file name or result.apk if the main file name includes spaces or some other invalid character. The name of the APK file is not really important. Before you distribute it you can rename it as you like.