App Name under icon

Solar2D Android
#21

Regarding the corrupted APK, I just took a 2nd look at the e-mail B&N sent me. I think I misunderstood. They said the APK you uploaded was fine until they re-signed it… and then it became corrupted. That’s the APK that they sent me for analysis. I apologize for the confusion. They’ve also sent me the APK that you’ve uploaded, as-is, without any modification and are asking me what might be causing it to go wrong.

Just out of curiosity, have you used any 3rd party tools such as “apktool” to modify the built APK?
The reason I ask is that tool has been known to remove needed settings from the APK.

And if you still think that spaces in the APK file name is the cause of this issue, then please feel free to stick to your guns. :slight_smile: It’s something I can ask them to re-investigate just in case.

Other than that, it sounds like you’ve got your bases covered in terms of display scaling and orientation handling. Just need to get past this one final hurdle. [import]uid: 32256 topic_id: 32063 reply_id: 127986[/import]

#22

Joshua,
no, we don’t use any other tools to modify the apk. The apk I upload is as it comes out of Corona the exact one they download from godaddy and works on their Nooks when bypassing their system.
I don’t think it is the spaces as it didn’t cause problems in Google Plauy or Amazon, they are the ones who came up with that possibility but seem to have rejected it themselves.
So they now have 2 apks from me: one that doesn’t support HD and one that does, the latter being the one that Tom asked me to send to him bypassing the upload system yesterday.
Which good one did they send you? Did you install/work on an HD Nook or just regular Nook?

Their zendesk support is hopeless - except for Tom Chavez, their twitter guy, who is very helpful - they don’t explain anything, they just tell to try this and that, never answer my questions, just push me off saying they are fixing the problem. 65 days and still waiting… [import]uid: 32063 topic_id: 32063 reply_id: 127988[/import]

#23

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]

#24

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]

#25

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]

#26

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]

#27

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]

#28

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]

#29

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:

  1. If you do letterbox your app, make sure to fill the letterbox area with graphics.
  2. Use “zoomEven” and make sure that you are not losing any important content on the sides of your app.
  3. 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]

#30

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]

#31

Joshua:
regarding upgrade to HD Nooks:

  1. 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
  2. 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)
  3. this app supports landscape only, so the 3rd problem shouldn’t occur
    [import]uid: 32063 topic_id: 32063 reply_id: 127983[/import]
#32

Regarding the corrupted APK, I just took a 2nd look at the e-mail B&N sent me. I think I misunderstood. They said the APK you uploaded was fine until they re-signed it… and then it became corrupted. That’s the APK that they sent me for analysis. I apologize for the confusion. They’ve also sent me the APK that you’ve uploaded, as-is, without any modification and are asking me what might be causing it to go wrong.

Just out of curiosity, have you used any 3rd party tools such as “apktool” to modify the built APK?
The reason I ask is that tool has been known to remove needed settings from the APK.

And if you still think that spaces in the APK file name is the cause of this issue, then please feel free to stick to your guns. :slight_smile: It’s something I can ask them to re-investigate just in case.

Other than that, it sounds like you’ve got your bases covered in terms of display scaling and orientation handling. Just need to get past this one final hurdle. [import]uid: 32256 topic_id: 32063 reply_id: 127986[/import]

#33

Joshua,
no, we don’t use any other tools to modify the apk. The apk I upload is as it comes out of Corona the exact one they download from godaddy and works on their Nooks when bypassing their system.
I don’t think it is the spaces as it didn’t cause problems in Google Plauy or Amazon, they are the ones who came up with that possibility but seem to have rejected it themselves.
So they now have 2 apks from me: one that doesn’t support HD and one that does, the latter being the one that Tom asked me to send to him bypassing the upload system yesterday.
Which good one did they send you? Did you install/work on an HD Nook or just regular Nook?

Their zendesk support is hopeless - except for Tom Chavez, their twitter guy, who is very helpful - they don’t explain anything, they just tell to try this and that, never answer my questions, just push me off saying they are fixing the problem. 65 days and still waiting… [import]uid: 32063 topic_id: 32063 reply_id: 127988[/import]

#34

I’m sorry that you are having such a bad experience.

I haven’t tried your working APK. I merely confirmed with B&N that the corrupted APK was really corrupted. I help them every once in a while with whatever questions they may send my way (and vice-versa). I know for a fact that they were looking into your APK issue last week. So, hopefully this will be resolved soon. [import]uid: 32256 topic_id: 32063 reply_id: 128192[/import]

#35

I’m sorry that you are having such a bad experience.

I haven’t tried your working APK. I merely confirmed with B&N that the corrupted APK was really corrupted. I help them every once in a while with whatever questions they may send my way (and vice-versa). I know for a fact that they were looking into your APK issue last week. So, hopefully this will be resolved soon. [import]uid: 32256 topic_id: 32063 reply_id: 128192[/import]