[Solved] Parse Error: There was a problem parsing the package

Thunkable Discuss
#1

Hi,

Tried to download .apk app from Thunkable X to android 4.2.2. However, getting the error “Parse Error: There was a problem parsing the package”. The security is disabled on the phone and I’ve tried testing .apk from different source and they are able to install. Is Thunkable X’s version not compatible with older androids?

1 Like
#2

Hi Terry,

Unfortunately, Thunkable X apps are only compatible with Android 5.0 and higher.
See the minimum requirements page here.

Do you have access to an Android device running Android OS 5.0 or higher to test this app on?

#3

oh I see, ok I’ve tried it, worked on higher androids (9)

1 Like
#4

I’m glad we could find an explanation so quickly!
I’m sorry that the app won’t run on your Android 4.2.2 device. :sleepy:

#5

@jane On another phone, I’ve upgraded and custom installed 6.0.1 Android (custom CyanogenMod GApp Marshmallow) but it still getting the same error and unable to install apk, any other suggestions?

I’m thinking perhaps there are certain dependencies that Thunkable rely on when unpacking the compiled .apk

1 Like
#6

Could you copy the URL of this app project from your browser and send it to me?

#7

@jane it was a project released from the mailing list
https://x.thunkable.com/copy/c8ad16e4ea93298840d1f04eed207d8b

1 Like
#8

Hi Terry,

I think this behavior is related to your app’s package name.
Because your app is called 4Hire, the package name is in the format com.thunkable.user.4Hire.

The segments of a package name need to start with letters, not numbers.
Try changing that last segment to something like .hire or .forhire.

To find your app’s package name:
Click your app’s logo in the upper left hand corner of the Components window to open an App Settings window on the right-hand side of the screen.

In this window, you’ll see a property called App (Bundle) ID.
This is your package name.

​

Screenshot+2019-04-15+at+11.53.00.png306×552
​

Let me know if that works!

4 Likes
#9

@jane wow ok it worked fine, both name and extension had to be none numerical

1 Like
#10

I think the project name should be fine - did you have to edit it after editing the package name?

1 Like
#11

changing the extension name alone, then apk install - did not work
changing the extension name and app name, then apk install - worked

1 Like
#12

Good to know! Thanks :grinning:

#13

Its working, its resolve my problem.
thanks dear.

2 Likes