PropTypes and createClass warnings in SDK 20

Hello, I upgraded my project to SDK 20 and I am getting warnings about PropTypes and React.createClass usage that look to be originating from Expo.js. None of my code uses React.createClass, PropTypes or checkPropTypes and I just got done checking all of my dependencies too. None of them are causing these warnings.

I found issue #365 where @dikaiosune mentioned that it was an upstream problem with react-native. Is that still the case?

Can you point out which code is causing this? I am curious because I also searched my entire node_modules directory for files containing PropTypes and createClass but I could not find any offending code…

Here are the contents of my package.json file:

  "name": "my-app",
  "version": "1.1.0-dev",
  "description": "My App",
  "author": {
    "name": "Wayne Bloss",
    "email": ""
  "license": "private",
  "main": "node_modules/expo/AppEntry.js",
  "scripts": {
    "test": "node ./node_modules/jest/bin/jest.js --watch"
  "jest": {
    "preset": "jest-expo"
  "dependencies": {
    "expo": "^20.0.0",
    "mustache": "2.3.0",
    "prop-types": "^15.5.10",
    "react": "16.0.0-alpha.12",
    "react-native": "",
    "react-native-htmlview": "",
    "react-native-modal-selector": "0.0.17",
    "react-native-platform-touchable": "^1.1.1",
    "react-navigation": "^1.0.0-beta.12",
    "wolfy87-eventemitter": "^5.2.2"
  "devDependencies": {
    "jest-expo": "~20.0.0"

and .babelrc:

  "presets": ["babel-preset-expo"],
  "env": {
    "development": {
      "plugins": ["transform-react-jsx-source"]

Hi! It does look like we’re tracking an issue to remove PropTypes from the SDK JS as well: Sorry about the confusion there!

Thank you for responding. The warnings have now disappeared after I upgraded the “expo” dependency to 20.1.2.

I was having a separate issue with an error “webBrowser.openBrowserAsync is not a function” and after I read this comment, I upgraded to the latest version of the expo-sdk that I saw on npm, which fixed both of my issues.

Now I’m just wondering why lists 20.1.2 as the latest release while shows 15.0.0 as the latest release…but that’s a separate topic. I’m sure there’s a good reason for it.

I’ve noticed it’s been that way for awhile with the github repo. I have a feeling their managing it another way now.