I do see the text. So everything should be fine, and is everything in my build.settings fine for the splash.
OK, another question can you know if it works beforehand before you post the app that the splash works, and is the build.settings good for the splash screen to work.
You should always build your app and test it on real devices before submitting it to a store. It’s the only way you can know that your app will work as expected. There are several items like the splash screen, ads, in-app purchases and more that can only be tested on a real device and not in the Corona Simulator.
I don’t see anything wrong in your build.settings that would lead me to believe there is a problem. But you won’t know until you test it.
Rob
OK, last question what do you mean by building and testing it out on a real device. Sorry for all these questions I’m just starting.
Another question if you are doing a build would I do it on android or windows, if I am working on a windows but wanting to upload my app for android devices. Also please answer my last question I am still a little confused about the concept.
The Corona Simulator is just that a simulator. It runs either on Windows or macOS and has to abide by the rules of that operating system. For instance, if you want to run Google in-app purchases. Google makes libraries that we can use to allow Android devices to make purchases. But that library does not work on Windows or macOS. Almost all Ad and analytics plugins fall into this category. The Facebook plugin does as well. It could be something not obvious like Windows and macOS have case insensitive operating systems while Android and iOS are both case sensitive. This can cause problems if you have a file named: Player.PNG on your computer, but in your Corona code you say:
local player = display.newImage(“player.png”)
It will work just fine in the simulator because neither Windows or macOS cares about if the letters are upper or lower case. When a person runs your app on their phone or tablet, it will crash because “player.png” is not equal to “Player.PNG”. These are easy mistakes to make when developing that won’t be exposed until you tell Corona to build your app and you plugin your test device (phone, tablet) into your computer via it’s USB charging cable and install your app on your device and test it there. The splash screen only works on a device, not the simulator. If you plan to have any text fields for people to type into, that behavior is really different between mobile operating systems and desktop/laptop operating system.
In other words, if you want to avoid a bunch of 1 star reviews, you should test your app on real device and don’t depend on the simulator as your only testing.
But this isn’t something you need to worry about today. Worry about your app first. The splash screen is probably one of the last things I’d work on.
Rob
You will do most of the work on Windows. Then with the Corona menu’s choose Build then choose Android. We will output a .apk file. There are multiple strategies on how to get the .apk file onto your device. There is a lot of information that we don’t need to repeat here in the forums. This is why we have our great Documentation, some of which are “Guides” designed to help walk you thru all of this. See:
https://docs.coronalabs.com/guide/index.html
As for this particular question, it’s covered in this guide: “Signing & Building – Android” https://docs.coronalabs.com/guide/distribution/androidBuild/index.html
Rob