Skip to content
This repository has been archived by the owner on Jan 18, 2024. It is now read-only.

expo init disregards --android-package and --ios-bundle-identifier arguments #824

Closed
kokeksibir opened this issue Jul 8, 2019 · 4 comments
Assignees

Comments

@kokeksibir
Copy link

Description

I am trying to set android package name and ios bundle identifier while initializing the project. Here is the commands I execute

$ expo --version
2.21.2
$ expo init testApp --android-package com.test.app --ios-bundle-identifier com.test.app
...

Expected Behavior

In app.json file I expect having android.package and ios.bundleIdentifier values to be set at least. When I choose a bare minimum project, I expect the given package name is also injected to relevant project files like android/app/build.gradle, AndroidManifest.xml and ios/<projectName>.xcodeproj.

Observed Behavior

Expected behavior defined above is not present at all. CLI disregards these arguments.

Environment

  Expo CLI 2.21.2 environment info:
    System:
      OS: macOS 10.14.5
      Shell: 3.2.57 - /bin/bash
    Binaries:
      Node: 10.15.3 - /usr/local/bin/node
      Yarn: 1.16.0 - /usr/local/bin/yarn
      npm: 6.9.0 - /usr/local/bin/npm
    IDEs:
      Android Studio: 3.4 AI-183.6156.11.34.5522156
      Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.8.3 => 16.8.3 
      react-native: 0.59.8 => 0.59.8 
    npmGlobalPackages:
      expo-cli: 2.21.2
@RohovDmytro
Copy link

Confirming.

@brentvatne brentvatne self-assigned this Dec 8, 2019
@brentvatne
Copy link
Member

indeed there appears to have been a regression here, thanks for the report

@te3
Copy link

te3 commented Mar 3, 2020

expo v3.13.1, '--android-package' not working.

@EvanBacon
Copy link
Contributor

#1878 (comment)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants