You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for providing a really easy way to use OneSignal notifications with React Native.
Please would it be possible to exclude the example AwesomeProject from the npm package.
When I use cloud services for continuous integration, I have observed that pod file in the example messes up the build. Also, it would be better, if the npm package only includes whatever is required to integrate and run with own project.
The text was updated successfully, but these errors were encountered:
That's a good idea, I'll add it to the TODO list.
Thanks.
On Apr 27, 2016 23:22, "Dan Jensen" notifications@github.com wrote:
Thank you for providing a really easy way to use OneSignal notifications
with React Native.
Please would it be possible to exclude the example AwesomeProject from the
npm package.
When I use cloud services for continuous integration, I have observed that
pod file in the example messes up the build. Also, it would be better, if
the npm package only includes whatever is required to integrate and run
with own project.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub #25
Thank you for providing a really easy way to use OneSignal notifications with React Native.
Please would it be possible to exclude the example AwesomeProject from the npm package.
When I use cloud services for continuous integration, I have observed that pod file in the example messes up the build. Also, it would be better, if the npm package only includes whatever is required to integrate and run with own project.
The text was updated successfully, but these errors were encountered: