We have not had any luck finding the root cause of this issue. It might be worthwhile, trying to do a native build, so our build servers are not in play. You don’t have to know any native programming, just copy the default App project to a folder specific for your build. Copy your Corona folder into the folder named “Corona” inside of App and then use Xcode and/or Android Studio to build your app. There is a little more work to download the plugins and get them into your project correctly, but once it’s set up it should work without issue.
Not really. Most of the “iphone” section of build.settings would go into the Xcode manage Info.Plist and you would just have to set up the various key-value pairs, but Xcode helps you do that. For the Android things, you would edit the Manfiest.xml file and put the various key-value pairs in there.
You would have to set up the various identifiers (package id for android bundle id, provisioning profile, etc. for iOS) in the various tools. Both have ways to build the app. Android is pretty straightforward, under Xcode you have to make an Archive. In both cases, all of those steps are not Corona specific, so there should be plenty of tutorials online that you can find with an internet search.
If you sell a bike telling us that it can go faster in traffic jams, and finally you recognize that it can not work because of a design flaw … I think that telling us that the solution is to put it in the trunk of our car to make the travel is not a possible solution.
With a recent build we already have to remove features from our applications because of incompatibilities between plugins. It starts to make a lot of problems, … unresolved. The use of Corona becomes more and more complicated.
We have multiple build servers, so the first thing we thought is that one server was different than another, but we have confirmed that a build ID that failed on server X also built successfully for the same user on the same server X. This has us scratching our head and we continue to research the issue. Perhaps at some point, there will be an “Ah ha!” moment and we can solve this.
I want this problem solved as much as you do, but given our difficulty finding this, I’m simply presenting you an alternative and very functional way for this to not be a problem for you. And frankly, since it seems this is only happening on Android builds and not iOS builds, you would only need to do native builds on Android and still use the simulator for iOS builds.
Perhaps changing the error dialog to something better (that didn’t fully stop the app from functioning) would be an interim step, if you can’t find the cause of the problem
To repeat what somebody mentioned earlier: I also notice that the message of the popup mentions an ID number which is the good one except that the last character is replaced by a “!”
Does this dialog list the FB app ID it’s trying to use? If so, the last character is getting replaced by a “!”. perhaps this is a useful clue to help your bug hunters
I’ve experienced this “Invalid Facebook App ID” error as well. Specifically on Android devices. Usually when I re-build with no other changes, the error goes away. So it seems like something inside Corona process.
When you fail, please report the build ID here. It would be helpful to have multiple build ID’s, ones that work and ones that don’t to help us track this down.
:wacko: