Updating to SDK 32 from a managed project

Expo SDK
1

I am using the managed method of getting my app onto the stores. It seems Play Console had an update that removed apps using call log and sms permissions. Apparently, SDK 32 resolves this issue.

I built my project a while ago and have been out of the Expo mindset, I don’t remember manually updating the SDK version or anything. How do I go about doing this? In my app.json I have:

"sdkVersion": "27.0.0",

In my package.json I have:

{
  "name": "my app name",
  "version": "0.1.0",
  "private": true,
  "devDependencies": {
    "react-native-scripts": "1.14.0",
    "jest-expo": "~27.0.0",
    "react-test-renderer": "16.3.1"
  },
  "main": "./node_modules/react-native-scripts/build/bin/crna-entry.js",
  "scripts": {
    "start": "react-native-scripts start",
    "eject": "react-native-scripts eject",
    "android": "react-native-scripts android",
    "ios": "react-native-scripts ios",
    "test": "jest"
  },
  "jest": {
    "preset": "jest-expo"
  },
  "dependencies": {
    "expo": "^27.0.1",
    "react": "16.3.1",
    "react-native": "^0.55.4",
    "react-native-map-link": "^2.1.0",
    "react-native-vector-icons": "^4.6.0",
    "react-navigation": "^2.9.1",
    "react-redux": "^5.0.7",
    "redux": "^4.0.0",
    "redux-thunk": "^2.3.0"
  }
}
2

Hey @jefffabiny,

You can find upgrade instructions in our blog posts: Expo SDK v32.0.0 is now available | by Eric Samelson | Exposition

We recommend upgrading sequentially as it tends to help identify any breakages that may occur in your project where as hopping from 27-32 may have you guessing on what is causing them. You are more than welcome to make the quick jump though and many have done it successfully. (You can find the upgrade instructions for each SDK here!

Cheers,
Adam

3

Hi,

I found those instructions and followed them sequentially to get to version 32. I got the app working in my expo client application. After running expo build:android and uploading the APK to Play Console, it says that I am requesting SMS permissions.

Shouldn’t the expo cli resolve this issue at SDK v32?

53%20PM
53%20PM1074×414 43.1 KB

4

Yeah, it should. Can you let me know what version of the expo-cli you are running and also paste your app.json contents here?

5

npm -v expo-cli

6.4.1

{
  "expo": {
    "name":"Roc Pub-n-Grub",
    "slug":"mobile-rocpubngrub",
    "sdkVersion": "32.0.0",
    "version":"1.0.2",
    "icon":"./assets/icon.png",
    "ios": {
      "bundleIdentifier": "com.rocpubngrub.pubgrub",
      "infoPlist": {
        "NSLocationAlwaysUsageDescription": "Used to determine how far away locations are from you."
      }
    },
    "android": {
      "permissions":[
        "ACCESS_COARSE_LOCATION",
        "ACCESS_FINE_LOCATION"
      ],
      "package": "com.rocpubngrub.pubgrub",
      "versionCode": 5
    },
    "splash": {
      "image": "./assets/splash.png",
      "backgroundColor": "#FFF",
      "resizeMode": "cover"
    }
  }
}
6

That is your NPM version. You’ll need to run expo --version to find out your expo-cli version number!

1 Like
7

Doh!

expo --version

2.11.7

8

Also, npm view expo version

32.0.6

9

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.