Skip to content

Flutterflow does not support mobile apps with package names "in.companyname.productname" #5563

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1 of 2 tasks
connecty-in opened this issue Mar 14, 2025 · 5 comments
Open
1 of 2 tasks
Assignees
Labels
status: stale type: bug Something isn't working.

Comments

@connecty-in
Copy link

connecty-in commented Mar 14, 2025

Can we access your project?

  • I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

Does not support creation of package names starting with "in".

Expected Behavior

Should support package names starting with "in".

Steps to Reproduce

  1. Try creating an app with package id starting with "in"

Reproducible from Blank

  • The steps to reproduce above start from a blank project.

Bug Report Code (Required)

N/A

Visual documentation

N/A

Environment

- FlutterFlow version: 5.2.8
- Platform:macOS
- Browser name and version: Chrome
- Operating system and version affected:

Additional Information

No response

@connecty-in connecty-in added the status: needs triage A potential issue that has not been confirmed as a bug. label Mar 14, 2025
Copy link
Collaborator

Hi! I'm sorry to hear you're experiencing this issue.

FlutterFlow doesn't allow the use of "in" in app package names, as it's a reserved keyword in both Java and Dart. This limitation arises from the package naming conventions in these programming languages, where certain keywords are restricted to prevent conflicts with the language syntax and reserved functionalities.

It's best to select an alternative that follows the conventions to avoid potential issues during development and deployment.

Best regards.

@connecty-in
Copy link
Author

connecty-in commented Mar 14, 2025

"in" word being a reserved word in the programming language should not limit the use of having it as a package name on the playstore or app store. Any or Most companies would like to use their domain in reverse order to uniquely identify the application. This would mean FlutterFlow does not support any product with domain ending in "in", which is the case for all domain names from India.

Along the same lines of you answer, since "in" is a reserved word in java, I do not see Google restricting package names starting with "in" in their App Store. Why does FlutterFlow do it?

From your support, I hear that this limitation was implemented to address deployment errors that occurred due to conflicts with certain reserved keywords.

FlutterFlow should not restrict whats already existing, but rather fix their product.
Example of an app with package name starting with "in": Amazon India (in.amazon.mShop.android.shopping)

@rzambroni rzambroni added status: not a bug This is not a bug. and removed status: needs triage A potential issue that has not been confirmed as a bug. labels Mar 14, 2025
@connecty-in
Copy link
Author

@rzambroni I see the status as "not a bug", But this is a bug. Connect with your development team and Product Management team to figure out a solution.

Copy link
Collaborator

Hi again,

I completely understand your concerns, and I truly appreciate your patience.

At the moment, this is a limitation of FlutterFlow. However, this is currently being reviewed by the engineering team, and I will keep you updated if there are any new developments.

Regards

@Juansarmi Juansarmi closed this as not planned Won't fix, can't repro, duplicate, stale Mar 19, 2025
@rzambroni rzambroni reopened this Mar 19, 2025
@rzambroni rzambroni removed the status: not a bug This is not a bug. label Mar 19, 2025
@rzambroni rzambroni added the type: bug Something isn't working. label Mar 19, 2025 — with Linear
@nathankrishnan nathankrishnan self-assigned this Mar 19, 2025
Copy link

This issue is stale because it has been open for 7 days with no activity. If there are no further updates, a team member will close the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: stale type: bug Something isn't working.
Projects
None yet
Development

No branches or pull requests

4 participants