Skip to content
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

[Android] Using a different package name to build fails to use the correct manifest file #17615

Closed
ycai2 opened this issue Jan 15, 2018 · 5 comments
Labels
Ran Commands One of our bots successfully processed a command. Resolution: Locked This issue was locked by the bot.

Comments

@ycai2
Copy link

ycai2 commented Jan 15, 2018

As a follow-up to #12820, filing a new issue about RN not using the correct manifest file.

Per @PCguru 's comment:

Whenever one of your flavors has a different package name #13169 still fails as it will use the packageName from the wrong AndroidManifest.xml. That is, it will not use the AndroidManifest.xml that was generated during build.

Currently, I'm able to use adb install to directly install the apk to a device to get around this issue.

Is this a bug report?

No

Have you read the Contributing Guidelines?

Yes

Environment

Environment:
OS: macOS Sierra 10.12.6
Node: 8.2.0
Yarn: Not Found
npm: 5.3.0
Watchman: 4.7.0
Xcode: Xcode 9.0 Build version 9A235
Android Studio: 3.0 AI-171.4443003

Packages: (wanted => installed)
react: ^16.0.0 => 16.0.0
react-native: ^0.51.0 => 0.51.0

Discussions have already happened in #5546, #13169, and #12820. @hramos please review this and advise what to do next.

@Nandez89
Copy link

Nandez89 commented Jan 19, 2018

I'm having the same issue app builds and installs but it won't open on the emulator because the package name is missing the applicationIdSuffix '.dev' added on buildTypes

my applicationId 'ca.myapp.ori'

BUILD SUCCESSFUL

Total time: 2 mins 0.982 secs

Running /Users/user/Library/Android/sdk/platform-tools/adb -s emulator-5554 reverse tcp:8081 tcp:8081
Starting the app on emulator-5554 (/Users/user/Library/Android/sdk/platform-tools/adb -s emulator-5554 shell am start -n ca.myapp.ori/ca.myapp.ori.MainActivity)...
Starting: Intent
Error type 3
Error: Activity class {ca.myapp.ori/ca.myapp.ori.MainActivity} does not exist.

Any help in how to fix this or work around it. I definitely need to keep the buildTypes

@scottschmitz
Copy link

It might be worth noting that #12820 appears to have been ignored because #13169 was merged but it looks like the import failed on #13169, nothing was updated, and then it was closed.

@react-native-bot
Copy link
Collaborator

Thanks for posting this! It looks like you may not be using the latest version of React Native, v0.53.0, released on January 2018. Can you make sure this issue can still be reproduced in the latest version?

I am going to close this, but please feel free to open a new issue if you are able to confirm that this is still a problem in v0.53.0 or newer.

How to ContributeWhat to Expect from Maintainers

@react-native-bot react-native-bot added Ran Commands One of our bots successfully processed a command. Stale There has been a lack of activity on this issue and it may be closed soon. labels Feb 24, 2018
@stale stale bot removed the Stale There has been a lack of activity on this issue and it may be closed soon. label Feb 24, 2018
@salmanwaheed
Copy link

salmanwaheed commented Feb 24, 2018 via email

@salmanwaheed
Copy link

salmanwaheed commented Feb 24, 2018 via email

@facebook facebook locked as resolved and limited conversation to collaborators Feb 24, 2019
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Feb 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Ran Commands One of our bots successfully processed a command. Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

5 participants