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

Using Galio with ejected app #68

Closed
matthintosh opened this issue Feb 11, 2019 · 5 comments
Closed

Using Galio with ejected app #68

matthintosh opened this issue Feb 11, 2019 · 5 comments

Comments

@matthintosh
Copy link

Bug description
Hello, I'm would like to use Galio component on an react-native ejected app.
Actually I have the issue which is : "The Expo SDK requires expo to run"

To Reproduce
Only trying to use Galio component on and ejected app

Screenshots
simulator screen shot - iphone x - 2019-02-11 at 14 50 02

Smartphone:

  • Device: [iPhone X]
  • Type of device: [simulator]
  • OS: [ios 11.3]
  • React-Native version: [e.g. 0.57.8]
  • Expo version: ejected app (expoKit ?)

Thanks for your help !

@harshrajk
Copy link

I second this.I am still waiting eagerly to use this without expo.

@palingheorghe
Copy link
Collaborator

Hi,

Galio has Expo as a dependency so it needs it in order to run. By removing Expo you leave no option for React-Native but to throw out that error.

If you must remove Expo I recommend doing the following. Clone the repo and copy the src folder inside a 'galio' folder in your app's root folder. Now... this isn't the best approach being the fact that the Icon and Button components have dependencies in Expo and you won't be able to use them. But this is the only workaround at the moment.

We will most certainly create a better, well-rounded workaround Expo. It is on our to-do list.

Thanks!

@matthintosh
Copy link
Author

Hi @palingheorghe,

Thank you for your reply.
I will probably wait for the the updated version of Galio because I would like to use buttons...

Regards,

@hetmann
Copy link
Collaborator

hetmann commented Feb 12, 2019

Or refactoring all the components to be Expo free :)

@palingheorghe
Copy link
Collaborator

Hi @hetmann,
As I said:

We will most certainly create a better, well-rounded workaround Expo. It is on our to-do list.
This is one of our goals.

I'll close this now because this question has been answered.

Thanks,
❤️

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

No branches or pull requests

4 participants