Are underscores in directory names no longer supported?

[dmglakewood]

I’m trying to use the following
 

system.pathForFile("\_someFolder", system.ResourceDirectory)

Every time I have an underscore in the file path though, it fails to load/find the file. Underscores used to be supported. Not sure if this is a bug or if I should change my code?

This works just fine on the simulator, but when ran on an android device it breaks. 

I’m using build 2019.3514

[rob]

I don’t know why it would have changed. Maybe Android 9 doesn’t like it. Maybe it’s something in the Gradle based build.system. I never understood the desire to put underscores at the beginning of names, though I guess for private members of a class it’s okay and if you’re doing any Python work, it’s kinda critical.

If your app doesn’t need _someFolder when someFolder will work, just change it and report a bug. It doesn’t seem like it needs to be a priority fix if there is an easy work around. If underscores anywhere in the file/path name breaks things then we should address that sooner than later.

Rob

[dmglakewood]

@rob

I don’t know why it would have changed. Maybe Android 9 doesn’t like it. Maybe it’s something in the Gradle based build.system. I never understood the desire to put underscores at the beginning of names, though I guess for private members of a class it’s okay and if you’re doing any Python work, it’s kinda critical.

If your app doesn’t need _someFolder when someFolder will work, just change it and report a bug. It doesn’t seem like it needs to be a priority fix if there is an easy work around. If underscores anywhere in the file/path name breaks things then we should address that sooner than later.

Rob

I don’t technically need it, but it’s nice to use so that it’s the first folder listed. I already converted them over, so it’s no biggie. I remember having the same issue with the early version of corona cards as well. 

I also found out that we can’t use double in our pacakge name. I guess that makes sense, but it sucks when I already have an app with double in the package name and can no longer update it. 

[rob]

I don’t know why it would have changed. Maybe Android 9 doesn’t like it. Maybe it’s something in the Gradle based build.system. I never understood the desire to put underscores at the beginning of names, though I guess for private members of a class it’s okay and if you’re doing any Python work, it’s kinda critical.

If your app doesn’t need _someFolder when someFolder will work, just change it and report a bug. It doesn’t seem like it needs to be a priority fix if there is an easy work around. If underscores anywhere in the file/path name breaks things then we should address that sooner than later.

Rob

[dmglakewood]

@rob

I don’t know why it would have changed. Maybe Android 9 doesn’t like it. Maybe it’s something in the Gradle based build.system. I never understood the desire to put underscores at the beginning of names, though I guess for private members of a class it’s okay and if you’re doing any Python work, it’s kinda critical.

If your app doesn’t need _someFolder when someFolder will work, just change it and report a bug. It doesn’t seem like it needs to be a priority fix if there is an easy work around. If underscores anywhere in the file/path name breaks things then we should address that sooner than later.

Rob

I don’t technically need it, but it’s nice to use so that it’s the first folder listed. I already converted them over, so it’s no biggie. I remember having the same issue with the early version of corona cards as well. 

I also found out that we can’t use double in our pacakge name. I guess that makes sense, but it sucks when I already have an app with double in the package name and can no longer update it.