-
Notifications
You must be signed in to change notification settings - Fork 15
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
2786: Upgrade dependencies #2912
base: 2786-upgrade-react-native-0.74
Are you sure you want to change the base?
2786: Upgrade dependencies #2912
Conversation
ac99b35
to
97108b2
Compare
97108b2
to
b5717ce
Compare
0bb5114
to
57fc3cc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code looks fine but I'm getting an error when trying to build it for iOS (Redefinition of module 'ReactCommon'), I'll try to fix that next week :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for updating 🚀
quickly tested an Android and firefox, everything works as expected.
@@ -9,7 +9,11 @@ export default class Page { | |||
* @param path path of the sub page (e.g. /path/to/page.html) | |||
*/ | |||
|
|||
open(path: string): Promise<string> { | |||
return browser.url(`${path}`) | |||
async open(path: string): Promise<string> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🙃 nitpick: i personally dislike mixing async/await and Promises like this, but no need to change it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How would you change this? I think I don't really mix async/await and promises, Promise
is just the correct return type of a async function.
9985839
to
2ef7df7
Compare
46d15c0
to
347d640
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, thanks for (still) slogging through that! Tested on Firefox and on real iOS, works nicely!
195daeb
to
d5b7b90
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately i can't build the app on ios with Xcode 15.4
Steps so far:
yarn install
pod install
(leads to differences in podfile.lock (ios folder), check my comment- "Clean product "in xcode
- run build
I was also checking this issue to fix it, but the resolved podfile.lock
is still differing from your verion and the error remains
reactwg/react-native-releases#284
But couldn't get it work.
Even i run a build without pod install
using your podfile.lock results in same error
native/ios/Podfile.lock
Outdated
@@ -34,33 +57,72 @@ PODS: | |||
- GCDWebServer/Core (= 3.5.4) | |||
- GCDWebServer/Core (3.5.4) | |||
- glog (0.3.5) | |||
- GoogleAppMeasurement (10.24.0): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if i run pod install
i don't get these resolved pods here. My podfile.lock differs a lot. Even i ran yarn install
before. But i'm using newer cocoapods version and
Urg, can you try deleting your node_modules and Pods and then reinstalling? |
One thing perhaps: After you installed the pods/did the installation for iOS @LeandraH, I reverted some upgrades and dependency resolutions. So differing pod file is probably okay, just commit them. |
It doesn't build for me anymore either, though that may partially be because I stupidly let my computer update Xcode this morning 🤦 I'm getting lots of "Could not build module XYZ" errors in React-RCTAppDelegate. Will try to figure that out tomorrow. |
Short description
Upgrade dependencies.
Proposed changes
Blocked
Error: Cannot set headers after they are sent to the client
stops the server in the CISide effects
Hopefully none.
Testing
Resolved issues
Fixes: #2786.