Aldo's Well-Known Member Licensed User Mar 27, 2021 #1 I have an app in App Store I try translate in B4I this App but the name is like: xxxx-xxxxx.app When i try to impost this package name I receive an error: "Package name non valido" I think the problem is the dash, but in the iTunes Connector i'm already this name, You have solution to me.
I have an app in App Store I try translate in B4I this App but the name is like: xxxx-xxxxx.app When i try to impost this package name I receive an error: "Package name non valido" I think the problem is the dash, but in the iTunes Connector i'm already this name, You have solution to me.
Semen Matusovskiy Well-Known Member Licensed User Mar 27, 2021 #2 Apple talks: The bundle ID string must contain only alphanumeric characters (A-Z, a-z, and 0-9), hyphens (-), and periods (.). So a hyphen, as it is, is not a problem. Upvote 0
Apple talks: The bundle ID string must contain only alphanumeric characters (A-Z, a-z, and 0-9), hyphens (-), and periods (.). So a hyphen, as it is, is not a problem.
Aldo's Well-Known Member Licensed User Mar 27, 2021 #3 Yes, for Apple no problem The problem is in B4I package name. Upvote 0
Semen Matusovskiy Well-Known Member Licensed User Mar 27, 2021 #4 I see - IDE does not allow. Meanwhile XCode allows hypens. I built as Similator Release App, then changed in XCODE bundle ID and ran it. No problems. Upvote 0
I see - IDE does not allow. Meanwhile XCode allows hypens. I built as Similator Release App, then changed in XCODE bundle ID and ran it. No problems.
Aldo's Well-Known Member Licensed User Mar 27, 2021 #5 So do you recommend me to run XCode and change my bundle id? Is this okay for Apple? Upvote 0
Semen Matusovskiy Well-Known Member Licensed User Mar 27, 2021 #6 It's obviously a bug. So, I recommend to write in iOS Bugs & Wishlist To use XCode, even if you have a local builder, is not very comfortable. Upvote 0
It's obviously a bug. So, I recommend to write in iOS Bugs & Wishlist To use XCode, even if you have a local builder, is not very comfortable.
Aldo's Well-Known Member Licensed User Mar 27, 2021 #7 How can I solve this problem? Do I have to remove the previous release and put a new one with the new package id? Upvote 0
How can I solve this problem? Do I have to remove the previous release and put a new one with the new package id?
Aldo's Well-Known Member Licensed User Mar 27, 2021 #8 Semen Matusovskiy said: It's obviously a bug. So, I recommend to write in iOS Bugs & Wishlist Click to expand... Do Thanks Upvote 0
Semen Matusovskiy said: It's obviously a bug. So, I recommend to write in iOS Bugs & Wishlist Click to expand... Do Thanks
Erel B4X founder Staff member Licensed User Longtime User Mar 28, 2021 #9 Try this: Create a new build configuration (Ctrl + B). Close the project. Edit the b4i file with a text editor and change the package name of that build. It will not work in debug mode but might work in release. Upvote 0
Try this: Create a new build configuration (Ctrl + B). Close the project. Edit the b4i file with a text editor and change the package name of that build. It will not work in debug mode but might work in release.
