Choose identifiers owned by your organization, such as com.example.customerportal, before configuring Firebase and creating store records. The inspected source uses com.flutex.customer.
In android/app/build.gradle.kts, update applicationId and review namespace. Update the package declaration and directory structure for MainActivity under android/app/src/main/kotlin/ to match your intended namespace. Check the manifest’s relative .MainActivity reference resolves correctly.
Search Android source and configuration for the old identifier, reviewing each match rather than applying an unrestricted replacement.
Open the Runner workspace in Xcode and change the Runner target’s bundle identifier for all build configurations. Review the RunnerTests identifier separately. Select the appropriate signing team and update provisioning as needed.
Register the new Android/iOS applications in your Firebase project. Replace platform configuration and regenerate lib/firebase_options.dart for those registrations. Update any relevant service configuration tied to the old identifiers.
Build both platforms and test startup, login, and push notifications.
Changing a display name is different from changing application identity. Once distributed, changing the application identifier generally creates a different app rather than an update for existing installations. Preserve the established identifier when releasing updates to the same app.