Continuing the discussion from EXDevMenuDelegateProtocol.h not found :
Please provide the following:
SDK Version: 37
Platforms(Android/iOS/web/all): iOS
pod ‘ExpoKit’,
:git => “GitHub - expo/expo: An open-source platform for making universal native apps with React. Expo runs on Android, iOS, and the web. ”,
:tag => “ios/2.15.4”,
:subspecs => [
“Core”
],
:inhibit_warnings => true
While upgrading to Expo 37 and building the iOS project, I get this error
EXDevMenuDelegateProtocol.h not found in EXKernel.h.
The file is not found in node_modules folder.
How do I resolve it?
I need to use the :tag => “ios/2.15.4” since this one contains the Facebook redirect corrections:
opened 09:10AM - 29 Oct 19 UTC
closed 06:31PM - 24 Apr 20 UTC
iOS
bug
Facebook
outdated
## 🐛 Bug Report
### Environment
```
Expo CLI 3.2.3 environment info:
… System:
OS: macOS 10.14.5
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 8.16.0 - ~/.nodebrew/current/bin/node
Yarn: 1.16.0 - ~/.nodebrew/current/bin/yarn
npm: 6.4.1 - ~/.nodebrew/current/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
IDEs:
Android Studio: 3.4 AI-183.6156.11.34.5522156
Xcode: 11.0/11A420a - /usr/bin/xcodebuild
npmPackages:
expo: ^35.0.0 => 35.0.0
react: 16.8.3 => 16.8.3
react-native: https://github.com/expo/react-native/archive/sdk-35.0.0.tar.gz => 0.59.8
react-navigation: ^3.11.0 => 3.11.0
npmGlobalPackages:
expo-cli: 3.2.3
```
**iOS Standalone AND iOS Expo Client**
### Steps to Reproduce
Must be logged out of Facebook in the browser, but logged in in the Facebook app
Facebook.logInWithReadPermissionsAsync, doesn’t come back to our app after flying to Facebook app.
This may or may not occur.
For now it only occurs on iOS standalone.
It’s pretty strange because it’s quite strange behavior and it hurts user acquisition opportunities.
This is fatal for our app.
### Expected Behavior
After logging in with Facebook, you are redirected to our app and the login process is executed
### Actual Behavior
Even after logging in on the Facebook app, it behaves like staying in the Facebook app.
The only way to get back to our app is to cancel, and of course the login process will fail.
### Sample code
``` javascript
import * as firebase from 'firebase';
import * as Facebook from 'expo-facebook';
const signinFacebook = async () => {
try {
const {
type,
token,
} = await Facebook.logInWithReadPermissionsAsync(
ENV.FACEBOOK_APP_ID,
{
permissions: ['public_profile', 'email'],
},
);
if (type === 'success') {
const credential = firebase.auth.FacebookAuthProvider.credential(token);
return firebase.auth().signInWithCredential(credential).catch((error) => {
throw error;
});
}
} catch (error) {
// ERROR
}
};
```
@adela88 it seems that Expokit 2.15.4 is missing the fix that was applied by this commit . To get that fix, you can change:
pod ‘ExpoKit’,
:git => “http://github.com/expo/expo.git”,
:tag => “ios/2.15.4”,
to
pod 'ExpoKit',
:git => "http://github.com/expo/expo.git",
:commit => "30eb0558ff6a77acf56bb045e98b84f6a5e1478a",
That being said, we really recommend switching over to the bare workflow once you can, the development experience is incomparable
1 Like
Thank you from the bottom of my heart.
This solution worked great and I was able to build.
Also the Facebook redirect problem it seems it got resolved after the build
1 Like
system
Closed
July 17, 2020, 3:00pm
5
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.