[RESOLVED] Public Release 1202: ERROR: Could not load provider (google) -- could it be supportedPlatforms no longer work?

Solar2D Daily Builds and Public Releases
#1

I’m using the public release build on Mac (OSX 10.7.5).  I downloaded the Corona SDK 1202 yesterday directly from daily build page.  

With the build 1202, I generated Android device build number of times yesterday, and I didn’t have any problem at all.  And I didn’t have any problem with a few Android build I generated this morning.

Then, all of a sudden, out of blue, for no reason whatsoever (because the code changes I made have nothing to do with gameNetwork API), my new Android build will no longer run, giving me the following error:

I/Corona  ( 8411): errorMessage = “ERROR: Could not load provider (google) due to the following reason: module ‘CoronaProvider.gameNetwork.google’ not found:resource (CoronaProvider.gameNetwork.google.lu) does not exist in archive\n\tno field package.preload[‘CoronaProvider.gameNetwork.google’]\n\tno file ‘(null)/CoronaProvider.gameNetwork.google.lua’\n\tno file ‘(null)/CoronaProvider.gameNetwork.google.lua’\n\tno file ‘/data/app-lib/com.company.myapp-2/libCoronaProvider.gameNetwork.google.so’\n\tno file ‘./CoronaProvider.gameNetwork.google.so’\n\tno file ‘(null)/CoronaProvider.gameNetwork.google.so’\n\tno file ‘/data/app-lib/com.company.myapp-2/libCoronaProvider.so’\n\tno file ‘./CoronaProvider.so’\n\tno file ‘(null)/CoronaProvider.so’.”

Just in case it might help, I deleted Corona SDK, and reinstalled it, but with the same result.  This is causing my work-I-need-to-do-right-away to a screeching halt.

By the way, I saw this post:  http://forums.coronalabs.com/topic/38247-module-coronaprovidergamenetworkgoogle-not-found-gpgs/

And that’s terrible.  What do I need to do (without reformatting my machine) to fix this.

And honestly, I don’t understand why Corona SDK suddenly starts causing me this issue while the very same Corona SDK worked earlier – and I didn’t change anything, except a few lines of code unrelated to the gameNetwork, and I didn’t do anything outside Corona SDK in-between the successful device builds and unsuccessful ones (except for posting on Corona forum about another API problem, meaning, all I did in-between is browsing online, searching for information to solve some Corona related problem and posting on Corona forum, which should have nothing to do with corrupting or causing any harm to CoronaProvider.gameNetwork.google in any way.)

Please help!!

Naomi

#2

I had a random bug one time after upgrading from 1079 to 1134.

I traced it back to using a “.” instead of a “:” somewhere in my code. (or visa-versa)

I used the wrong syntax initially, but the code allowed for it. When they fixed the code to make it behave correctly, thats when I got all the crashing.

#3

Strange.  I reverted back to 1196, and tried it – but it failed with exact same error.  I then switched back to 1202, and tried one more time, and it worked this time.

And oh, I did change the build.settings code just to see if it fixes it:

The one I used yesterday and earlier today:  

[“CoronaProvider.gameNetwork.google”] = { publisherId = “com.coronalabs”, supportedPlatforms = { android = true }, },

The one I changed to and now working:

[“CoronaProvider.gameNetwork.google”] = { publisherId = “com.coronalabs” },

So, was it a back end build server issue that needed fixing (and got fixed), or was it that supportedPlatforms no longer works today?  

I don’t know and I don’t have time to sort this out.  I need to work on getting the fixes in and deployed – so I’m just going to remove supportedPlatforms bit from build.settings altogether.  (I’d rather uncommenting than not having my build work at all out of blue like this…)

And, if it was something to do with build server issue and not the supportedPlatforms issue, please do let me know so that I will use the supportedPlatforms (instead of cumbersome uncommenting process) in the future.

Naomi

#4

@MochiBits, thanks for sharing your experience.  It sounds like the issue I dealt with is unrelated to the use of “.” or “:” – because only change I made before and after was editing my build.settings (one with supportedPlatforms and one without.)  And mind you, one with supportedPlatforms worked yesterday, and it worked earlier today, until it stopped working.  

My hunch is, the issue was something to do with build server, but then, who knows?  It’s only a hunch unless I’m told otherwise, and I’m going with the code that is working now rather than tempt fate.

Naomi 

#5

I had a random bug one time after upgrading from 1079 to 1134.

I traced it back to using a “.” instead of a “:” somewhere in my code. (or visa-versa)

I used the wrong syntax initially, but the code allowed for it. When they fixed the code to make it behave correctly, thats when I got all the crashing.

#6

Strange.  I reverted back to 1196, and tried it – but it failed with exact same error.  I then switched back to 1202, and tried one more time, and it worked this time.

And oh, I did change the build.settings code just to see if it fixes it:

The one I used yesterday and earlier today:  

[“CoronaProvider.gameNetwork.google”] = { publisherId = “com.coronalabs”, supportedPlatforms = { android = true }, },

The one I changed to and now working:

[“CoronaProvider.gameNetwork.google”] = { publisherId = “com.coronalabs” },

So, was it a back end build server issue that needed fixing (and got fixed), or was it that supportedPlatforms no longer works today?  

I don’t know and I don’t have time to sort this out.  I need to work on getting the fixes in and deployed – so I’m just going to remove supportedPlatforms bit from build.settings altogether.  (I’d rather uncommenting than not having my build work at all out of blue like this…)

And, if it was something to do with build server issue and not the supportedPlatforms issue, please do let me know so that I will use the supportedPlatforms (instead of cumbersome uncommenting process) in the future.

Naomi

#7

@MochiBits, thanks for sharing your experience.  It sounds like the issue I dealt with is unrelated to the use of “.” or “:” – because only change I made before and after was editing my build.settings (one with supportedPlatforms and one without.)  And mind you, one with supportedPlatforms worked yesterday, and it worked earlier today, until it stopped working.  

My hunch is, the issue was something to do with build server, but then, who knows?  It’s only a hunch unless I’m told otherwise, and I’m going with the code that is working now rather than tempt fate.

Naomi