App with expansion obb shows "Not licensed" alert

Solar2D Android
#1

My published app has one expansion obb (544MB), and it shows “Not licensed” at start up like below.

[sharedmedia=core:attachments:4654]

In another project, I followed instructions below, and expansion file works good.

https://docs.coronalabs.com/daily/guide/distribution/buildSettings/index.html#expansion-files

https://docs.coronalabs.com/daily/guide/basics/configSettings/index.html#app-licensing

 

And now I did same set up, but got bad result.

I don’t understand what the difference.

 

I worry about I made some mistake in uploading app and obb to Google Developer Console.

 

When uploading first .obb to Google Developer Console, I made a mistake.

I did not insert licensing library in main.lua like below.

   local licensing = require( “licensing” )

   licensing.init( “google” )

Published app still not work good, showing “Not licensed” alert.

After inserting licensing library, upload new .apk and 2nd .obb to Developer Console.

At this time, I made 2nd mistake.

I applied both 1st obb and new 2nd obb.

Published app not work good, showing “Not licensed” alert.

At this time, which obb is referenced ?

Again, I built apk with new version code, uploaded apk and newest obb, 

But published app still not work good, showing “Not licensed” alert.

Please give some advice.

Thanks.

#2

Got same problem today and I have no solution.

#3

Here is what one of our engineer’s had to say:
 

Regarding the “not licensed” issue, this means that the Google licensing library thinks that the app was not purchased/downloaded from Google Play.  If you install the APK on your device by hand (such as via “adb install”), then you need to set up your Google Play account on that device as a test account via the “Google Play Developer Console” (that’ where you upload/publish your app).  You do this under the “Settings” tab (this is a global tab, not a per-app tab) where you can add user accounts for testing.  You can all set the “License Test Response” there as well.  If you change it to “Licensed”, then you’ll get past this error.  You can also set it up to “Not Licensed” for testing purposes.

Rob

#4

Got same problem today and I have no solution.

#5

Here is what one of our engineer’s had to say:
 

Regarding the “not licensed” issue, this means that the Google licensing library thinks that the app was not purchased/downloaded from Google Play.  If you install the APK on your device by hand (such as via “adb install”), then you need to set up your Google Play account on that device as a test account via the “Google Play Developer Console” (that’ where you upload/publish your app).  You do this under the “Settings” tab (this is a global tab, not a per-app tab) where you can add user accounts for testing.  You can all set the “License Test Response” there as well.  If you change it to “Licensed”, then you’ll get past this error.  You can also set it up to “Not Licensed” for testing purposes.

Rob