-
-
Notifications
You must be signed in to change notification settings - Fork 153
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
[🐛] config IDs when using app.config.js/app.config.ts rather than app.json #462
Comments
+1 |
Hello 👋, to help manage issues we automatically close stale issues. This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?
Thank you for your contributions. |
This comment was marked as resolved.
This comment was marked as resolved.
1 similar comment
+1 |
I believe reasonable PRs are merged here - if you post a PR we can discuss, and there seems to be a lot of interest from the |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
hi @mikehardy, thanks for your answer. but unfortunately I cannot push PRs. iOS is fixed, have to write documentation and for android i need help from other supporters. |
@megacherry I am not sure why you can't do PRs? I believe all you need to do is fork the repo, do the work on a branch then make a PR? It is a fork-based repo |
Hello 👋, to help manage issues we automatically close stale issues. This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?
Thank you for your contributions. |
@mikehardy: The PR is created. Took me some time because it's my first PR on GitHub. :) |
Solved by #517 |
What happened?
First of all: sorry if any information or similar is missing. I try my best :)
I'm writing because I currently switched from app.json to app.config.js/app.config.ts (I use expo). Mainly to serve different environments.
Then when I went to rebuild my project, I got an error: "error: ios_app_id key not found in react-native-google-mobile-ads key in app.json. App will crash without it."
Then I searched for related issues and found the following issue: #370
But that doesn't help me because firstly the issue is closed and secondly the pull request is only for Android (and not merged). I currently have the problems on iOS.
I then looked at what it fails and found that a parsing of Javascript Object Literal Syntax is not so trivial. Especially something like this: "process.env.APP_NAME || 'myapp'".
So I came up with the following solution (ios_config.sh):
I patched the ios_config.sh locally. But that would be only the part for iOS. If the solution sounds good, then we have to adjust the readme and think of something for Android as well.
How can I best help you at this point?
Platforms
Android and iOS
React Native Info
Are your using Typescript?
package.json
not relevant at this point
app.json
ios/Podfile
No response
android/build.gradle
No response
android/app/build.gradle
No response
android/settings.gradle
No response
AndroidManifest.xml
No response
The text was updated successfully, but these errors were encountered: