Space in Application Name, Android / Windows

Hey Corona Team,

I stuck some hours having a problem when trying to install my Android app with ADB to my device on Windows.

ADB tells me that it cannot find the file, although the path was completely right…

…seemingly!

My app’s name has a space character, e.g. “my app.apk”. This name was set in the “Application Name” textfield on build window in Corona Simulator.

I figured out that Corona does not set a “regular” space between the two words (0x20 hex value) is sets a non break space (hex 0xC2 0xA0). On Windows the optical result is the same, but there is no way to say that to my console window. 

Is this a volitational behaviour?

Is there a way to handle this? At the moment I have to manually replace the space with the “right” space.

Best regards

  Chris

I doubt this is something we are doing.  It sounds like something Windows is doing.  I’ll ask Engineering to make sure.

Rob

We replace some characters in the name of the .apk with visually equivalent characters so that we don’t restrict app names to a “safe” subset.

The easiest way to enter such a name in the Console is either to copy and paste it from Windows Explorer or use TAB completion (in this case type “my<TAB>” and the name will be completed correctly).

It’s likely we’ll allow localization of app names in the future and then “special” characters would not be an issue.

I don’t understand?  If I put a space (ASCII  decimal value 32) and I build to Android I get my app name with another type of space (ASCII decimal value 160) and then I’m forced to manually replace it with the proper space value.  Why can’t Corona build with the proper Space character as I had intended???  There’s going to be a lot more frustrated people running into the same issue and pulling their hair out because they can’t install via ADB

Why are you “forced to manually replace it”?

It’s worked this way for quite a while and you’re the first to notice.

Your right I’m not forced, I could copy the name and paste in terminal to copy the adb, but I’m constantly testing new builds and have multiple versions sitting around that I like to keep things consistent. It’s just doesn’t make sense why corona is changing changing the space character and it’s annoying.  This seemed to have occurred during the summer, and I’ve just recently switched to a new version of Corona, wasted an hour or two just trying to understand what was going on.

Same here, suck on this problem 1-2 hours.

In my case I got some scripts who cannot handle this changed space, so I also have to rename the file after every build.

It looks like space might have been a character too far in our efforts to make app names more flexible and not tied to the host operating system.  I’ll stop the Simulator changing spaces in an upcoming Daily Build.

This is fixed in Daily Build 2014.2494

I doubt this is something we are doing.  It sounds like something Windows is doing.  I’ll ask Engineering to make sure.

Rob

We replace some characters in the name of the .apk with visually equivalent characters so that we don’t restrict app names to a “safe” subset.

The easiest way to enter such a name in the Console is either to copy and paste it from Windows Explorer or use TAB completion (in this case type “my<TAB>” and the name will be completed correctly).

It’s likely we’ll allow localization of app names in the future and then “special” characters would not be an issue.

I don’t understand?  If I put a space (ASCII  decimal value 32) and I build to Android I get my app name with another type of space (ASCII decimal value 160) and then I’m forced to manually replace it with the proper space value.  Why can’t Corona build with the proper Space character as I had intended???  There’s going to be a lot more frustrated people running into the same issue and pulling their hair out because they can’t install via ADB

Why are you “forced to manually replace it”?

It’s worked this way for quite a while and you’re the first to notice.

Your right I’m not forced, I could copy the name and paste in terminal to copy the adb, but I’m constantly testing new builds and have multiple versions sitting around that I like to keep things consistent. It’s just doesn’t make sense why corona is changing changing the space character and it’s annoying.  This seemed to have occurred during the summer, and I’ve just recently switched to a new version of Corona, wasted an hour or two just trying to understand what was going on.

Same here, suck on this problem 1-2 hours.

In my case I got some scripts who cannot handle this changed space, so I also have to rename the file after every build.

It looks like space might have been a character too far in our efforts to make app names more flexible and not tied to the host operating system.  I’ll stop the Simulator changing spaces in an upcoming Daily Build.

This is fixed in Daily Build 2014.2494