callstack / super-app-showcase

Monorepository template for super app development with React Native and Re.Pack
MIT License
382 stars 63 forks source link

No bundle URL present #65

Closed saravanan6137 closed 9 months ago

saravanan6137 commented 9 months ago

Environment

[catalog] [CatalogServer] Server listening at port 3000

Description

Even through I followed the steps,

  1. yarn from root directory.
  2. yarn pods from root directory.
  3. changed host app "start" command to this -> "start": "react-native webpack-start --port=8082" since 8081 is already used by some other app (mac app)
  4. Then from root directory package.json I ran -> "run:host:ios": "yarn workspace host run ios --port=8089 --simulator='iPhone 14 Pro Max'"
  5. Build is successful and simulator launches but I get error in simulator No bundle url present and I see the dev-server which are running are not responding to the app I ran.

All the dev server are running and iOS build also successful

Reproducible Demo

jbroma commented 9 months ago

Hey @saravanan6137,

I think you used wrong port in the run ios command, you should use port 8082 instead of 8089 as specified above.

saravanan6137 commented 9 months ago

Hi @jbroma Thanks for the reply. yes I tried that also. "run:host:ios": "yarn workspace host run ios --port=8082 --simulator='iPhone 14 Pro Max'"

still same issue. if possible can give the steps you followed to run this template or any solution you aware of? if I run android, the app just gets stuck on the launch screen. Thanks!

saravanan6137 commented 9 months ago

Hi jakub, Thanks for your reply.

Yes I tried like you said just now where I see some improvement (getting first response from host app). But still the error remains the same. Please check the screenshots of how I set up the template. [image: Screenshot 2023-09-27 at 6.07.19 PM.png] [image: Screenshot 2023-09-27 at 6.07.37 PM.png] [image: Screenshot 2023-09-27 at 6.06.05 PM.png]

On Wed, Sep 27, 2023 at 5:08 PM Jakub Romańczyk @.***> wrote:

Hey @saravanan6137 https://github.com/saravanan6137,

I think you also need to provide --port 8082 to the react-native ios command in the host app, please check that and let me know whether this resolved your issue.

— Reply to this email directly, view it on GitHub https://github.com/callstack/super-app-showcase/issues/65#issuecomment-1737007403, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQOF6KZGREEIIDGIWCF2VPLX4PUIVANCNFSM6AAAAAA5IW6RAQ . You are receiving this because you were mentioned.Message ID: @.***>

saravanan6137 commented 9 months ago
Screenshot 2023-09-27 at 6 10 21 PM Screenshot 2023-09-27 at 6 10 53 PM Screenshot 2023-09-27 at 6 11 03 PM

Guys please checkout my setup screenshots

jbroma commented 9 months ago

All looks good to me and it should work, try rebuilding the ios app

saravanan6137 commented 9 months ago

Please let me know the steps I followed are correct.

  1. clone the project

  2. Run yarn from the root directory.

  3. Run yarn pods from the root directory.

  4. Go to host app -> package.json -> change like this "ios": "react-native run-ios --port 8082", "start": "react-native webpack-start --port=8082"

  5. Go to main package.json -> change like this "run:host:ios": "yarn workspace host run ios --port=8082 --simulator='iPhone 14 Pro Max'",

  6. Run yarn start

  7. Run "run:host:ios" script.

On Wed, Sep 27, 2023 at 6:30 PM Jakub Romańczyk @.***> wrote:

All looks good to me and it should work, try rebuilding the ios app

— Reply to this email directly, view it on GitHub https://github.com/callstack/super-app-showcase/issues/65#issuecomment-1737133877, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQOF6K7C5J4TLUSGS5LHAQ3X4P56DANCNFSM6AAAAAA5IW6RAQ . You are receiving this because you were mentioned.Message ID: @.***>

jbroma commented 9 months ago

For ios these steps look correct, I will try to run this on my local setup and get back to you

saravanan6137 commented 9 months ago

Thanks.

jbroma commented 9 months ago

I've verified that the app runs correctly on my setup with this changed port. I think you can also try few more things:

From my POV, this looks like a networking issue and I'm not sure I will be able to assist you with that

saravanan6137 commented 9 months ago

Thanks! Works now.