PACKAGE and VERSION control not in SYNC

Bugs and Other Issues
1

IT has been a nightmare to UPLOAD an .aab FILE on playstore CONSOLE. Everytime it says a version error. i went through few versions to get over this error but failed. I have created a new version of APP on inventor. How do i get this file to be upload in CONSOLE without creating a NEW LISTING which is another nightmare. I tried several times and each time it complains about a version and app bundle not in sync.

Another issue i want to raise is why dont you not allow proper numbering of version control? normally at testing stages it should be V0.1, V.02 etc and and when in production V1.0, V2.0. I think you need to go by industrlai standards. Its absolutely horendous! and this is

what copilot had to say " just make sure the internal package name (set by MIT) is consistent with the app listing in Play Console." SYNC THIS for heavans sake so that developers can concentrate on developing APPs rather than attempting to solve petty problems such as this and advise GOOGLE to have TEST DATABASE to test APPs before publishing.

2

Always use the same project name

Version code for Google Play is an integer value, just increment it for each new version

Version name can be anything of your choice, e g. V0.01, V2.0, V3 super edition, as you like

Yes exactly
Use the same project name and the sane login to get the same package name

the package name for App Inventor apps is
appinventor.ai_<email address before @>.<project name>

Taifun

3

your CHART retrieval from tinyDB module when loaded to our block area lack lot of block coding - why???? missing blocks PLEASE FIX THIS asap
Sunil V

4

Without being ARROGANT make changes to your dumb version control

  1. ALL test versons must begin with 0.1 and new versions 0.2, 0.3 etc.
  2. NO NEED OF TWO stupid verrsin mane and version code or whatever!
  3. PRODUCTION versions must begin with 1.0 and new versions 2.0. if its a minor change it can go as a PATCH 1.1 etc.
    Thers is no point in a fEEDBACK if you FAIL to implement what we experineced IBM programmers/system analysts observe the flaws in your IDE. COMPRENDE???
5

You have to complain with Google

Just set whatever you want in version name, 0.1 or 0.2 or 1.0 or 2.2
And increment version number with each release, i.e. 1, 2, 3, ...

Taifun

6

If you're invited to a meal, you're certainly not going to complain about the food; you either eat what's served or you don't. That's your choice. If you see that countless users have been enjoying this food for many years, you, as a relatively new user, could simply adapt to their menu. A small note: You use capital letters very often in your posts. These are interpreted as shouting and are not welcome here.

7

Your version numbering system is COMPLETLY wrong!
Test version should never start with 1.0. It should be 0.1 (you take my suggestion or reject it)
any new version should be 0.2 and so on.
Only Production versions should start with 1.0 and and increments depending on a path or new verison - say a minor change can go as 1.1 etc (accept my suggestion or reject it)
Also Display the version number on the screen when the APP is running thats very important. (accept or reject it)
It is wise for you guys to be OPEN for suggestions and also correcting your flaws. rather rathan saying " if you dont like the menu (i.e. MIT inventor) go to another restaurant" thats downwrite unprofessional!

8

I would recommend adopting a different tone. Your suggestions will hardly be considered if presented in this rude and impertinent manner.

1 Like
9

they were rude so this was a return.

when they demosnstrate unprofessionalism - you too respond in the same manner.

its not the delvery that matters its the commodity

cheers!

10

No need to open a new topic as you already stated this twice. I close and unlist this.

1 Like
11

In your cheeky post, you could at least have clarified what you were even talking about: VersionCode or VersionName? The latter, by the way, can be set arbitrarily.

12

A bread line gourmet.

1 Like