A new react-native release on jcenter with version 0.42.3-atlassian-1 is seems to be breaking RN builds with version less than 0.42.3 #14225

gShrey · 2017-05-27T12:01:33Z

Creating new issue from #14223 for better visibility.

For android projects, react native is added as dependency in gradle by using "com.facebook.react:react-native:+" and are linked to android source in react-native package.
But few hours ago, a new release with version 0.42.3-atlassian-1 was added on bintray was added. This is seems to be breaking on React native android build before version 0.44 .
I have checked on 0.41, 0.39.1 and 0.42.1. All projects are failing with same error:

Could not find com.atlassian.mobile.video:okhttp-ws-compat:3.7.0-atlassian1.

Any resolution with jcenter on this will be helpful.

kishanj918 · 2017-05-27T12:41:23Z

I can confirm it happening also on 0.40.0 on android. But app is able to run on ios.

hjumeau · 2017-05-27T12:51:18Z

I'm using the 0.38 version of react-native and I have the same issue.

bestotem · 2017-05-27T13:43:30Z

I have the same issue today, my version is 0.42

Knorcedger · 2017-05-27T14:19:25Z

Same issue here

david50407 · 2017-05-27T14:38:50Z

Try the temporary fix here #14223 (comment)

kishanj918 · 2017-05-27T14:49:51Z

@david50407 thanks david that worked.

timscott · 2017-05-27T16:24:10Z

Same issue on 0.41.0.

muneebsajjad · 2017-05-27T17:35:57Z

same issue on 0.41.2

freckletonj · 2017-05-27T18:46:07Z

same issue despite @david50407 's fix, tried on a smattering of RN versions 0.22 -> 0.44

rszalski · 2017-05-27T19:15:52Z

Upgrading react-native from 0.42.0 to 0.42.3 fixed this error for me.

xwartz · 2017-05-28T04:40:06Z

Any update on this? @brentvatne

weiliank · 2017-05-28T10:39:18Z

same issue on RN 0.39.2

EslamNasser · 2017-05-28T17:34:57Z

Same issue on RN 0.40.0

metelski · 2017-05-28T20:06:19Z

Agree with @rszalski - try upgrading react-native to 0.42.3. This worked for me as well (upgrading from 0.42.0)

pentateu · 2017-05-29T06:50:27Z

Hi @SathishSundharam,
This is a workaround, not a definitive solution.

The solution is for them to fix the repository.

arunkumarrmrj · 2017-05-29T06:55:59Z

"com.atlassian.mobile.video" is not avaible on maven right now. To run your project you need to update it

Update your react and react-native version to in your package.json file

"react": "16.0.0-alpha.3",
"react-native": "0.43.1",

Then remove node_modules and do a npm install again

Let me know if it works for you

bucketclan · 2017-05-29T07:12:25Z

Not everybody is in a situation to upgrade their projects. So, upgrading cannot be the solution.

inakianduaga · 2017-05-29T07:22:19Z

"com.atlassian.mobile.video" is not avaible on maven right now. To run your project you need to update it
Update your react and react-native version to in your package.json file
"react": "16.0.0-alpha.3",
"react-native": "0.43.1",
Then remove node_modules and do a npm install again

I actually have

"react": "16.0.0-alpha.6",
"react-native": "0.43.3",

and I'm still getting the same error (wiped npm_modules as well). Is the fix specific to 0.43.1?

LisitaEugen · 2017-05-29T11:49:36Z

Same issue here with "react": "15.3.2","react-native": "^0.36.0" Any idea to workaround this?

muneebsajjad · 2017-05-29T11:56:59Z

I upgraded to version "react-native": "^0.44.0" which solve this problem but I will not recommend this as it will break your navigator and app will crash. There is workaround for that too that come at cost of extra code work.

…

On Mon, May 29, 2017, 4:50 PM lisitaeugen ***@***.***> wrote: Same issue here with "react": "15.3.2","react-native": "^0.36.0" Any idea to workaround this? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#14225 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACHtxUOxc_xXme-iQ-53C1kfuS4RB0wbks5r-rEDgaJpZM4NoVRI> .

rezaarifian · 2017-05-29T12:03:23Z

I cannot release or build project react native.
Same issue here with "react-native": "0.32.0" "react-native-cli: 2.0.1" "react": "15.3.1",

jamescoq · 2017-05-29T12:05:37Z

The workaround mentioned in #14223 (comment) seems to work only for app created via react-native scripts. When integrating react-native app into existing android app there is a subsequent error:
`A problem occurred configuring project ':mobile'.

Could not resolve all dependencies for configuration ':mobile:_dev1DebugApk'.
A problem occurred configuring project ':react-native-vector-icons'.
> Could not resolve all dependencies for configuration ':react-native-vector-icons:_debugPublishCopy'.
> Could not find com.facebook.react:react-native:0.38.0.
Required by:
project :react-native-vector-icons
`

chris-pikul · 2017-05-29T12:07:03Z

Desperately need a fix for this. Upgrading RN isn't an option (time constraints) so as of RN: 0.35 I can't get it to work. The build.gradle fix suggested did nothing for me. I'm speciffically getting it from react-native-image-picker package. But the atlasion package is the same as being reported here.

Missing Dependency:
com.atlassian.mobile.video:okhttp-ws-compat:3.7.0-atlassian1

Referenced Package:
react-native-image-picker

RN: 0.35.0

bilalsyed001 · 2017-05-29T12:10:24Z

@ChrisPikul510 dirty fix: goto node_modules/react-native-image-picker and change this line to compile "com.facebook.react:react-native:0.20.1" -> https://github.com/react-community/react-native-image-picker/blob/develop/android/build.gradle#L48

chris-pikul · 2017-05-29T12:18:20Z

@bilalsyed001 Wow, that worked. But it is dirty. It just brought me to another dependency. This time react-native-photo-view not sure how far I want to chase the rabbit down this hole. I'm gonna see how painful the jump from RN 0.35 to 0.42 is... Will report back.

kibot914 · 2017-05-29T12:44:19Z

Very Desperate, I think I have to work overnight, come on
0.26 -> 0.44

rezaarifian · 2017-05-29T12:50:17Z

it's work for me with "react-native": "0.32.0" "react-native-cli: 2.0.1" "react": "15.3.1",
edit on android/build.gradle

allprojects {

repositories {
    mavenLocal()
    jcenter()
    maven {
        // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
        url "$rootDir/../node_modules/react-native/android"
    }

    configurations.all {
        resolutionStrategy {
            eachDependency { DependencyResolveDetails details ->
                if (details.requested.group == 'com.facebook.react' && details.requested.name == 'react-native') {
                    details.useVersion "0.32.0" // Your real React Native version here
                }
            }
        }
    }
}

}

khannasaransh · 2017-05-29T13:07:08Z

I am having same issue as mentioned by @jamescoq

Error:Failed to resolve: com.facebook.react:react-native:0.42.3

tiofabby · 2017-05-29T13:12:17Z

Same here, setting up version to my local one: details.useVersion "0.41.2" fixed the issue.

monumentyusuf · 2017-05-29T13:17:52Z

same with @khannasaransh ;
Cant find RN 0.42.3 on maven
Error:Failed to resolve: com.facebook.react:react-native:0.42.3

kibot914 · 2017-05-29T13:21:10Z

https://bintray.com/bintray/jcenter/com.facebook.react%3Areact-native#

tszajna0 · 2017-05-29T14:28:58Z

I managed to fix the issue with build.gradle:

allprojects {
    repositories {
        mavenLocal()
        mavenCentral()
        jcenter()
        maven {
            // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
            url "$projectDir/../../node_modules/react-native/android"
        }
        maven {
          // Because some dependencies are differently nested
          url "$projectDir/../../../node_modules/react-native/android"
        }
        maven {
          // Because some other dependencies are nested in yet another way
          url "$projectDir/../../../../node_modules/react-native/android"
        }
    }
}

Nasty, but worked for me; you may need to try with more or less ../

kibot914 · 2017-05-29T14:29:26Z

Remember : $rootDir/../node_modules/react-native/android

$rootDir instead of $projectDir

tszajna0 · 2017-05-29T14:47:47Z

@kibot914 right; that's an explanation why the original solution ~~above~~ didn't work for me. Thanks a lot!

ghost · 2017-05-30T13:28:42Z

If you are on RN 0.41.2 then applying the temporary fix that @david50407 suggests above solves the issue right away. No other change required.

simaoneves · 2017-05-30T16:08:26Z

Using RN 0.36.1 and @david50407 temporary fix above solves the issue.

shrutic · 2017-05-30T19:21:14Z

The temporary fix by @david50407 does not work for me as I am using a custom fork of 0.43.3 react-native. I get "Failed to resolve: com.facebook.react:react-native:0.43.3"

nowtech · 2017-05-30T22:15:17Z

Upgrading from react-native 0.42.0 to 0.42.3 worked for me

gShrey · 2017-05-31T03:38:49Z

After contacting bintray and asking them to remove invalid release. They have deleted 0.42.3-atlassian-1 release from jcenter repo. App should build without any need of workaround now.

godspeedelbow · 2017-05-31T07:01:38Z

Great! Would there be anything *we* could do to prevent this from happening in the future?

piyush565 · 2017-05-31T08:00:35Z

i cant start development server even after build successful in windows. i updated react-native version to 0.42.3, message comes 'loading dependency graph, done' in packager. #help

matthiasprieth · 2017-05-31T08:34:19Z

I also had no possibility to change to RN >= 0.44.0 i got it working by switching to version in package.json

    "react": "~15.4.1",
    "react-native": "0.42.0",

and putting this in my build.gradle

    configurations.all {
        resolutionStrategy {
            eachDependency { DependencyResolveDetails details ->
                if (details.requested.group == 'com.facebook.react' && details.requested.name == 'react-native') {
                    def file = new File("$rootDir/../node_modules/react-native/package.json")
                    def version = new groovy.json.JsonSlurper().parseText(file.text).version
                    details.useVersion version
                }
            }
        }
    }

AdrianZghibarta · 2017-05-31T12:01:39Z

Guys, did you tried one more time? cause now all my projects are running fine, it seems that the maven node was restored.

monotv · 2017-05-31T12:05:20Z

All good in the hood now for me ("react-native": "^0.39.2").

piyush565 · 2017-06-02T09:40:24Z

app running cool with version react- 15.3.2, react-native- 0.35.0, but it asks for reactnativepropsregistry.js file missing or changed. So, i put "import { ReactNativePropRegistry } from 'react-native';" in node modules/react native easy grid/utils/ compute props.js... Happy coding after struggling for 5 days straight to figure out the issue solution.

abhrp-hs · 2017-10-27T05:02:31Z

Hi, this issue is happening again, cannot download react-native:0.49.3 from maven, the repos do not exist on both maven and bintray. Using react-native:+ downloads v0.20.1 which is a very old version and is breaking all my react native projects.

ABKZR · 2018-01-08T14:24:05Z

Same Problem
HELP me to solve this

What went wrong:
A problem occurred configuring project ':app'.

Could not resolve all dependencies for configuration ':app:_debugApk'.
A problem occurred configuring project ':react-native-vector-icons'.
> Could not resolve all dependencies for configuration ':react-native-vector-icons:classpath'.
> Could not resolve com.android.tools.build:gradle:2.3.+.
Required by:
Login_Page:react-native-vector-icons:unspecified
> Could not resolve com.android.tools.build:gradle:2.3.+.
> Failed to list versions for com.android.tools.build:gradle.
> Unable to load Maven meta-data from https://jcenter.bintray.com/com/android/tools/build/gradle/maven-metadata.xml.
> Could not GET 'https://jcenter.bintray.com/com/android/tools/build/gradle/maven-metadata.xml'.
> Permission denied: connect

david50407 mentioned this issue May 27, 2017

Error while run with okhttp-ws-compact #14223

Closed

kishanj918 mentioned this issue May 27, 2017

react-native run-android fails. #14226

Closed

s2t2 mentioned this issue May 27, 2017

Build get error with com.atlassian.mobile.video oblador/react-native-vector-icons#480

Closed

jackfiallos mentioned this issue May 28, 2017

Build fails - Could not find com.atlassian.mobile wkh237/react-native-fetch-blob#375

Open

MyTotoro mentioned this issue May 29, 2017

Cannot find entry file index.ios.js [index.android.js] in any of the roots #14246

Closed

piyushcoader mentioned this issue May 30, 2017

Build fails wscodelabs/react-native-call-log#5

Closed

gShrey closed this as completed May 31, 2017

facebook locked as resolved and limited conversation to collaborators May 31, 2018

react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 18, 2018

A new react-native release on jcenter with version 0.42.3-atlassian-1 is seems to be breaking RN builds with version less than 0.42.3 #14225

A new react-native release on jcenter with version 0.42.3-atlassian-1 is seems to be breaking RN builds with version less than 0.42.3 #14225

Comments

gShrey commented May 27, 2017

kishanj918 commented May 27, 2017 • edited

hjumeau commented May 27, 2017

bestotem commented May 27, 2017

Knorcedger commented May 27, 2017

david50407 commented May 27, 2017

kishanj918 commented May 27, 2017

timscott commented May 27, 2017

muneebsajjad commented May 27, 2017

freckletonj commented May 27, 2017

rszalski commented May 27, 2017 • edited

xwartz commented May 28, 2017

weiliank commented May 28, 2017

EslamNasser commented May 28, 2017

metelski commented May 28, 2017 • edited

pentateu commented May 29, 2017

arunkumarrmrj commented May 29, 2017

bucketclan commented May 29, 2017

inakianduaga commented May 29, 2017 • edited

LisitaEugen commented May 29, 2017

muneebsajjad commented May 29, 2017 via email

rezaarifian commented May 29, 2017

jamescoq commented May 29, 2017

chris-pikul commented May 29, 2017

bilalsyed001 commented May 29, 2017

chris-pikul commented May 29, 2017

kibot914 commented May 29, 2017 • edited

rezaarifian commented May 29, 2017

khannasaransh commented May 29, 2017

tiofabby commented May 29, 2017

monumentyusuf commented May 29, 2017 • edited

kibot914 commented May 29, 2017

tszajna0 commented May 29, 2017

kibot914 commented May 29, 2017

tszajna0 commented May 29, 2017 • edited

ghost commented May 30, 2017

simaoneves commented May 30, 2017

shrutic commented May 30, 2017

nowtech commented May 30, 2017

gShrey commented May 31, 2017

godspeedelbow commented May 31, 2017 via email

piyush565 commented May 31, 2017

matthiasprieth commented May 31, 2017

AdrianZghibarta commented May 31, 2017

monotv commented May 31, 2017 • edited

piyush565 commented Jun 2, 2017

abhrp-hs commented Oct 27, 2017 • edited

ABKZR commented Jan 8, 2018

kishanj918 commented May 27, 2017 •

edited

rszalski commented May 27, 2017 •

edited

metelski commented May 28, 2017 •

edited

inakianduaga commented May 29, 2017 •

edited

kibot914 commented May 29, 2017 •

edited

monumentyusuf commented May 29, 2017 •

edited

tszajna0 commented May 29, 2017 •

edited

monotv commented May 31, 2017 •

edited

abhrp-hs commented Oct 27, 2017 •

edited