Skip to content

ProxyComponent has no propType for native prop RCTMap.followUserLocation of native type BOOL #6613

New issue
New issue
Closed
Closed
ProxyComponent has no propType for native prop RCTMap.followUserLocation of native type BOOL#6613
Labels
Platform: iOSiOS applications.Ran CommandsOne of our bots successfully processed a command.Resolution: LockedThis issue was locked by the bot.
@JakeRawr

Description

@JakeRawr
JakeRawr
opened on Mar 23, 2016
Contributor

I recently upgraded RN from v0.19 to v0.22.

When I run the simulator, this error popped up.

screen shot 2016-03-23 at 1 37 52 pm

Error log that shows in the xcode:

2016-03-23 13:54:20.818 [error][tid:com.facebook.React.JavaScript] `ProxyComponent` has no propType for native prop `RCTMap.followUserLocation` of native type `BOOL`
If you haven't changed this prop yourself, this usually means that your versions of the native code and JavaScript code are out of sync. Updating both should make this error go away.
2016-03-23 13:54:20.819 [fatal][tid:com.facebook.React.RCTExceptionsManagerQueue] Unhandled JS Exception: `ProxyComponent` has no propType for native prop `RCTMap.followUserLocation` of native type `BOOL`
If you haven't changed this prop yourself, this usually means that your versions of the native code and JavaScript code are out of sync. Updating both should make this error go away.
2016-03-23 13:54:20.845 [info][tid:com.facebook.React.JavaScript] Running application "________" with appParams: {"rootTag":1,"initialProps":{}}. __DEV__ === true, development-level warning are ON, performance optimizations are OFF
2016-03-23 13:54:20.847 [error][tid:com.facebook.React.JavaScript] Application ________ has not been registered. This is either due to a require() error during initialization or failure to call AppRegistry.registerComponent.
2016-03-23 13:54:20.848 [fatal][tid:com.facebook.React.RCTExceptionsManagerQueue] Unhandled JS Exception: Application IOS_99GAMERS has not been registered. This is either due to a require() error during initialization or failure to call AppRegistry.registerComponent.

I've removed the node_modules and reinstall v0.22.
Same error occurred.

I've been looking for a fix to this issue (thought I'm not the only one). But I couldn't find reported bug that's related to this issue.

I'm currently running on:
React Native v0.22,
xcode ios simulator,
Mac

If you need more detail, i'll reply within minutes. Thanks

Activity

charpeni

charpeni commented on Mar 23, 2016

@charpeni
charpeni
on Mar 23, 2016
Contributor

I can take a look at this tomorrow.

charpeni

charpeni commented on Mar 23, 2016

@charpeni
charpeni
on Mar 23, 2016
Contributor

@facebook-github-bot label ios

facebook-github-bot
added
Platform: iOSiOS applications.
Ran CommandsOne of our bots successfully processed a command.
on Mar 23, 2016
JakeRawr

JakeRawr commented on Mar 24, 2016

@JakeRawr
JakeRawr
on Mar 24, 2016
ContributorAuthor

Thank you,

Update: (5:00 pm, 3/23/16)
I changed the code
from

var React = require('react-native');
var {
  ...
  MapView,
  ...
} = React;

to

import React, {
  ...
  MapView,
  ...
} from 'react-native';

seems to make the problem go away. I do not have an explanation tho.

More Update: (5:17 pm, 3/23/16)
I didn't know I had Enabled Hot Reloading

screen shot 2016-03-23 at 5 13 19 pm

After I disable hot reloading, changing back to

var React = require('react-native');
var {
  ...
  MapView,
  ...
} = React;

works.

So, I'm assuming the issue is with HMR

BrianJoyce

BrianJoyce commented on Mar 24, 2016

@BrianJoyce
BrianJoyce
on Mar 24, 2016

Similar issue here.
screen shot 2016-03-24 at 00 58 20

charpeni

charpeni commented on Mar 24, 2016

@charpeni
charpeni
on Mar 24, 2016
Contributor

@BrianJoyce do you have Hot Reloading enabled ?

BrianJoyce

BrianJoyce commented on Mar 24, 2016

@BrianJoyce
BrianJoyce
on Mar 24, 2016

No I don't.
screen shot 2016-03-24 at 01 35 27

nikolasburk

nikolasburk commented on Mar 24, 2016

@nikolasburk
nikolasburk
on Mar 24, 2016

I have the exact same issue as @BrianJoyce after starting a new project this morning. Could it have to do with the recent Xcode update?

BrianJoyce

BrianJoyce commented on Mar 24, 2016

@BrianJoyce
BrianJoyce
on Mar 24, 2016

@nikolasburk yeah it's possible i guess, or something to do with react 0.22 and lastest xcode. Will check out a few 0.21 projects later to see if it's an issue with 0.21

nikolasburk

nikolasburk commented on Mar 24, 2016

@nikolasburk
nikolasburk
on Mar 24, 2016

I was using "react-native": "^0.21.0" in my package.json. I now updated to 0.22, deleted all npm modules, reran npm install and then restarted the app with npm start -- -- reset-cache and this actually solved the issue for me.

BrianJoyce

BrianJoyce commented on Mar 24, 2016

@BrianJoyce
BrianJoyce
on Mar 24, 2016

@nikolasburk thanks! Did that, then uninstalled and re-installed watchman and it seems to have done the trick. Thanks again.

charpeni

charpeni commented on Mar 24, 2016

@charpeni
charpeni
on Mar 24, 2016
Contributor

Since it seems resolved and caused by bad sync between js bundle and the app, I'll close it.

If you think this is a persistent bug, just reflag it.

charpeni

charpeni commented on Mar 24, 2016

@charpeni
charpeni
on Mar 24, 2016
Contributor

@facebook-github-bot close

facebook-github-bot

facebook-github-bot commented on Mar 24, 2016

@facebook-github-bot
facebook-github-bot
on Mar 24, 2016
Contributor

@charpeni tells me to close this issue. If you think it should still be opened let us know why.

facebook-github-bot
closed this as completedon Mar 24, 2016
facebook-github-bot
added
Ran CommandsOne of our bots successfully processed a command.
on Mar 24, 2016
chrisnojima

chrisnojima commented on Mar 25, 2016

@chrisnojima
chrisnojima
on Mar 25, 2016
Contributor

Clearing the cache seems to have no affect for me. Turning off hot reloading does fix it. Using 0.22.2 and xcode Version 7.3 (7D175)

gopidon

gopidon commented on Apr 16, 2016

@gopidon
gopidon
on Apr 16, 2016

npm start -- -- reset-cache worked for me. XCode 7.3, RN - 0.23.1

Antsanirina

Antsanirina commented on Jun 2, 2016

@Antsanirina
Antsanirina
on Jun 2, 2016

same issues here.. any of your solutions is working . :/ (android studio 2.1.1)

masterkrang

masterkrang commented on Jul 21, 2016

@masterkrang
masterkrang
on Jul 21, 2016

This won't be a solution for everybody, but the "constructor has no proptype for native prop X.X" is a common issue when running new projects. Make sure to close out all of your projects, and reset the cache in the simulator, try again. This usually works for me.

dcurletti

dcurletti commented on Oct 1, 2016

@dcurletti
dcurletti
on Oct 1, 2016

I also currently having this issue.

my2dieer

my2dieer commented on Mar 22, 2017

@my2dieer
my2dieer
on Mar 22, 2017

i have met the same issue. but i found the problem was that i had ran another project early. when i reload the terminal ,it works.

budiga

budiga commented on Apr 22, 2017

@budiga
budiga
on Apr 22, 2017

reload the terminal,works for me!thanks! @my2dieer

durgarao150

durgarao150 commented on May 15, 2018

@durgarao150
durgarao150
on May 15, 2018

what is the solution for this issue?

facebook
locked as resolved and limited conversation to collaborators on May 24, 2018
react-native-bot
added
Resolution: LockedThis issue was locked by the bot.
on Jul 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Platform: iOSiOS applications.Ran CommandsOne of our bots successfully processed a command.Resolution: LockedThis issue was locked by the bot.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @BrianJoyce@masterkrang@chrisnojima@nikolasburk@gopidon

        Issue actions
          `ProxyComponent` has no propType for native prop `RCTMap.followUserLocation` of native type `BOOL` · Issue #6613 · facebook/react-native