Anthony Mittaz

I hacked around it but it is definitely not a good solution: https://github.com/sync/bb8/commit/876ed2c2b2b7d94922c83c1d87e69c3569341640

I didn't like the fact that i have to create a fake subscription to see if pool is working... I've opened a PR let me know what you think: https://github.com/khuey/bb8/pull/71

@khuey i can't see any usage of the dedicated_connection in the codebase, do you have a sample somewhere ?

it works locally on your compute with `now dev` if you build (don't need to do it statically) and copy the binary where needed

https://github.com/sync/graphql-server-workshop-2018, run: - esy - esy now-prepare - now dev

@jordwalke before i do any more work does this look ok ?

OK looking at the test failing it seems that shell with a >4.7.0 requirement is a bad idea. Will look at doing something else. I know there is something i...

@davesnx off course feel free to take over. But there is more to it than just fixing merge conflicts. I've been trying to find time to go back to it...

I was debugging the cli and saw this: https://github.com/expo/expo/blob/6f9afd41bac6a41c29f7afa2468db9c70d9de953/packages/%40expo/cli/src/start/platforms/ios/AppleDeviceManager.ts#L144 ``` private async getApplicationIdFromBundle(filePath: string): Promise { // TODO: Implement... return EXPO_GO_BUNDLE_IDENTIFIER; } ``` And it seems that this is what's...

Here is the path-package fix if anyone is experiencing the same issue: [@expo+cli+0.2.6.patch.zip](https://github.com/expo/expo/files/9274684/%40expo%2Bcli%2B0.2.6.patch.zip)