What do I need to add to the build.settings file to set the name that will appear
under the icon for app after installed on Android devices?
I know how to do that for iOS, but can’t find it for Android. [import]uid: 32063 topic_id: 32063 reply_id: 332063[/import]
I never put anything in the build.settings for this. I just let Corona SDK use the folder name where main.lua lives. If I want my app to be Called “Fred”, I make sure to name the folder “Fred” and that’s what I get for the name.
[import]uid: 19626 topic_id: 32063 reply_id: 127764[/import]
Thanks Rob. I always get the name that I use as app name at the top in the corona build screen for Nook. That becomes the apk name and the app name under the icon.
I am having big rejection issues from Nook with one app. They said it is their problem but can’t seem to fix their system such that my app gets approval. It seems they can’t handle apks that have a space in the name and are working to fix it.
I don’t want to change the name as I want to keep it with the space when it appears under the icon. The Nook support guy said it can be set using the Android manifests, but hasn’t told me how it is done. So I am trying to figure out. Maybe he is wrong. [import]uid: 32063 topic_id: 32063 reply_id: 127780[/import]
Luciane, after you compile the app into an APK, change the name of the .apk file to anything you want. It doesn’t matter what it is called. The name of the app is stored inside the APK in the AndroidManifest.xml file, and the name of the .apk file itself is ignored by Nook and everyone else. [import]uid: 160496 topic_id: 32063 reply_id: 127781[/import]
Thanks Mike!
And the app name that is stored inside the apk is taken from the name I used in the corona build screen right? Should I worry about the folder name?
I will try that once they allow me to upload a new apk. For now they asked me not to try again as they want to fix their system for whatever the problem is. This has been going on for more than 60 days now!! [import]uid: 32063 topic_id: 32063 reply_id: 127784[/import]
Yes, the name is taken from that Corona dialog box. Folder name doesn’t matter.
Good luck. [import]uid: 160496 topic_id: 32063 reply_id: 127786[/import]
I never put anything in the build.settings for this. I just let Corona SDK use the folder name where main.lua lives. If I want my app to be Called “Fred”, I make sure to name the folder “Fred” and that’s what I get for the name.
[import]uid: 19626 topic_id: 32063 reply_id: 127764[/import]
Thanks Rob. I always get the name that I use as app name at the top in the corona build screen for Nook. That becomes the apk name and the app name under the icon.
I am having big rejection issues from Nook with one app. They said it is their problem but can’t seem to fix their system such that my app gets approval. It seems they can’t handle apks that have a space in the name and are working to fix it.
I don’t want to change the name as I want to keep it with the space when it appears under the icon. The Nook support guy said it can be set using the Android manifests, but hasn’t told me how it is done. So I am trying to figure out. Maybe he is wrong. [import]uid: 32063 topic_id: 32063 reply_id: 127780[/import]
Mike is correct. The name that you enter into the Android build window is the app’s display name. That is, it’s the name that appears on the Android screen. It even supports unicode characters and symbols such as +, -, :, etc.
It is okay to rename the APK file after it is built. The name of the APK does not have to match the application’s display name. In fact, I highly recommend that the APK file name use English characters and avoid spaces/symbols. This prevents upload failures with certain app stores. [import]uid: 32256 topic_id: 32063 reply_id: 127937[/import]
Luciane, after you compile the app into an APK, change the name of the .apk file to anything you want. It doesn’t matter what it is called. The name of the app is stored inside the APK in the AndroidManifest.xml file, and the name of the .apk file itself is ignored by Nook and everyone else. [import]uid: 160496 topic_id: 32063 reply_id: 127781[/import]
Thanks Mike!
And the app name that is stored inside the apk is taken from the name I used in the corona build screen right? Should I worry about the folder name?
I will try that once they allow me to upload a new apk. For now they asked me not to try again as they want to fix their system for whatever the problem is. This has been going on for more than 60 days now!! [import]uid: 32063 topic_id: 32063 reply_id: 127784[/import]
Yes, the name is taken from that Corona dialog box. Folder name doesn’t matter.
Good luck. [import]uid: 160496 topic_id: 32063 reply_id: 127786[/import]
Thanks Joshua.
Nook has locked my app - I can’t do new uploads - until they fix the problem in their system that is corrupting my apk file. It may be the space in the apk file name or it may not.
I had no issues with the space in Google Play or Amazon. It just went through without any hicups. [import]uid: 32063 topic_id: 32063 reply_id: 127946[/import]
I’m sorry to hear that. I hope it’ll get resolved soon.
If you don’t mind me asking, can you confirm with B&N that it was the space in the APK file name that broke the upload? If that’s the case, then we can look into changing our build system to replace spaces with underscores in the file name to prevent this issue from happening again. [import]uid: 32256 topic_id: 32063 reply_id: 127951[/import]
I will try but it seems they don’t even know what the exact problem is. Their zendesk support is very bad. Tom Chavez, who posts their Tweets, is very helpful and is trying to push for a resolution. I will post here when I know. I’ve let Tom know that Corona team also wants to know. [import]uid: 32063 topic_id: 32063 reply_id: 127959[/import]
Just to let you know, I’ve e-mailed B&N about this too. I’m just trying to get as much info about this as possible so that we can avoid this issue in the future. [import]uid: 32256 topic_id: 32063 reply_id: 127964[/import]
Joshua: I have another app in the nook store that I want to update to run the HD Nooks. I have a new build already with latest Corona. (BTW I never got a message from them to say I have to resubmit)
Did it need to be a new version - it is currently 1.2, does it need to be 1.3? Or do I just resubmit the new apk with the same version just changing the meta-data supported platforms to include the 2 new Nooks?
Is there a simple guide of needed steps?
(in case you are wondering how a test driver can publish apps, we have another corona account (Pro) that does the builds, etc)
thanks. [import]uid: 32063 topic_id: 32063 reply_id: 127969[/import]
B&N just got back to me and said that spaces are allowed in APK file names. They said that the APK that they received from you was corrupted. They sent me your APK and I confirmed this as well. Perhaps it was a bad file transfer and you just need to upload it again.
In order to support the new Nook HD/HD+ devices, you just need to build with the newest Corona daily build. The APK that Corona builds will support all Nook devices.
Now, the 2nd most common reason apps get rejected on Nook HD/HD+ is because they use letterboxed scaling. B&N wants apps to be fullscreen, unless they’re video players. So, you’ll need to do one of the following with your app:
- If you do letterbox your app, make sure to fill the letterbox area with graphics.
- Use “zoomEven” and make sure that you are not losing any important content on the sides of your app.
- Do not use dynamic content scaling.
You can find B&N official device specs for the Nook HD/HD+ via the link below…
https://nookdeveloper.barnesandnoble.com/product/nook-device-specs.html
The 3rd most common reason for app rejection is due to a bug in Corona with app that support both portrait and landscape orientations. It’s a bug that occurs on all Android tablets (except Kindle Fire HD) running on Android OS version 3.0 or higher. What happens is that Corona’s content gets misplaced after an orientation change. This happens because the bottom navigation bar moves with the screen, causing a resize of the display width/height to occur which Corona currently does not handle correctly.
The only known work-around for this issue at the moment is to set up your app with a fixed orientation such as “portrait” and “portraitUpsideDown”… or “landscapeRight” and “landscapeLeft”.
Regarding B&N’s versionCode policy, I don’t know the answer to that. A quick search on B&N developer site didn’t turn up anything. [import]uid: 32256 topic_id: 32063 reply_id: 127971[/import]
Joshua:
The apk they sent you was corrupted by their system. The apk I submitted and resubmitted already many, many times is a working apk.
Two of their people downloaded the same apk from my website (I can email you the link so you can install it if you want, tell me where to email it to), installed in their nooks and it worked.
I got this from Tom: “There was something in it that broke our script and ended up with a corrupt apk after repackaging so its something we need to fix.”
They told me to create a completely new submission which I did and it was rejected by the same reason with the same working apk.
They’ve locked my app so I can’t do anymore uploads as per their instructions until they fix their problem.
So I am very surprised they said the apk came corrupt from me.
And this has been going on for 65 days!!
I think I will forget about updating to the HD Nooks for a while until they get their act together. [import]uid: 32063 topic_id: 32063 reply_id: 127980[/import]
Joshua:
regarding upgrade to HD Nooks:
- we use letterbox and fill the letterbox area. We did that when going from iPad (initial target) to iPhone and various Android, so it is built in the app already
- we used corona 935 for the HD builds (the apk they are dealing with is not yet the HD one, even though Tom asked me for the HD version for new tests)
- this app supports landscape only, so the 3rd problem shouldn’t occur
[import]uid: 32063 topic_id: 32063 reply_id: 127983[/import]