[jitsi-dev] jitsi meet android app unmet dependency


#1

Hi guys,

Just did a fresh git clone and am having issues with webpack version.
I installed nodejs 6 on ubuntu and after doing npm install I get unmet
dependency for webpack

├── react-i18next@3.1.0
└── UNMET PEER DEPENDENCY webpack@1.14.0

Anyone else getting this error?

Cheers


#2

I'm running node 7.9.0, npm 4.5.0 on macOS and I don't get such an error.

···

On Wed, Apr 26, 2017 at 4:20 AM, Peter Villeneuve <petervnv1@gmail.com> wrote:

└── UNMET PEER DEPENDENCY webpack@1.14.0


#3

I ran into the same issue today using node 6.10.x, deleting
node_modules folder and running npm install fixed it.

···

On Wed, Apr 26, 2017 at 4:20 AM, Peter Villeneuve <petervnv1@gmail.com> wrote:

Hi guys,

Just did a fresh git clone and am having issues with webpack version.
I installed nodejs 6 on ubuntu and after doing npm install I get unmet
dependency for webpack

├── react-i18next@3.1.0
└── UNMET PEER DEPENDENCY webpack@1.14.0

Anyone else getting this error?

Cheers

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#4

Hi Lyubomir,

I updated to node 7.9.0 and am running npm 4.2.0 on ubuntu 17.03 and after
running npm install I get the following error message:

Starting JS server...
Building and installing the app on the device (cd android && ./gradlew
installDebug)...

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'jitsi-meet-react'.

Could not resolve all dependencies for configuration ':classpath'.

   > Could not download gradle-core.jar
(com.android.tools.build:gradle-core:2.2.3)
      > Could not get resource '
https://jcenter.bintray.com/com/android/tools/build/gradle-core/2.2.3/gradle-core-2.2.3.jar
'.
         > Could not GET '
https://jcenter.bintray.com/com/android/tools/build/gradle-core/2.2.3/gradle-core-2.2.3.jar
'.
            > sun.security.validator.ValidatorException: No trusted
certificate found

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or
--debug option to get more log output.

BUILD FAILED

Total time: 7.197 secs
Could not install the app on the device, read the error above for details.
Make sure you have an Android emulator running or a device connected and
have
set up your Android development environment:
https://facebook.github.io/react-native/docs/android-setup.html

I'll update npm to your version to see if it makes any difference.

Cheers,
Peter

···

On Wed, Apr 26, 2017 at 1:41 PM, Lyubomir Marinov < lyubomir.marinov@jitsi.org> wrote:

On Wed, Apr 26, 2017 at 4:20 AM, Peter Villeneuve <petervnv1@gmail.com> > wrote:
> └── UNMET PEER DEPENDENCY webpack@1.14.0

I'm running node 7.9.0, npm 4.5.0 on macOS and I don't get such an error.

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#5

That's a gradle error that I haven't hit myself. Judging by
"sun.security.validator.ValidatorException: No trusted certificate
found", it sounds like there's a environment/system problem with
someone's certificate.

···

On Wed, Apr 26, 2017 at 9:38 AM, Peter Villeneuve <petervnv1@gmail.com> wrote:

running npm install I get the following error message:

Starting JS server...
Building and installing the app on the device (cd android && ./gradlew
installDebug)...

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'jitsi-meet-react'.

Could not resolve all dependencies for configuration ':classpath'.

   > Could not download gradle-core.jar
(com.android.tools.build:gradle-core:2.2.3)
      > Could not get resource
'https://jcenter.bintray.com/com/android/tools/build/gradle-core/2.2.3/gradle-core-2.2.3.jar'.
         > Could not GET
'https://jcenter.bintray.com/com/android/tools/build/gradle-core/2.2.3/gradle-core-2.2.3.jar'.
            > sun.security.validator.ValidatorException: No trusted
certificate found

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or
--debug option to get more log output.

BUILD FAILED

Total time: 7.197 secs
Could not install the app on the device, read the error above for details.
Make sure you have an Android emulator running or a device connected and
have
set up your Android development environment:
https://facebook.github.io/react-native/docs/android-setup.html

I'll update npm to your version to see if it makes any difference.


#6

Thanks Damian,

Indeed deleting the node_modules folder and running npm install fixed it
and I can now compile the app.
However, as soon as it starts on my S6 running 7.0 I get the red screen
error:

"Could not get BatchedBridge, make sure your bundle is packaged correctly"

I'm using java-8-openjdk-amd64, node 7.9.0 and running npm 4.2.0.

I noticed during compilation a whole bunch of warnings regarding seemingly
out of date libraries.

What environment are you using that works well (ie what jdk, node, npm,
etc)?

Cheers,
Peter

···

On Wed, Apr 26, 2017 at 7:46 PM, Damian Minkov <damencho@jitsi.org> wrote:

I ran into the same issue today using node 6.10.x, deleting
node_modules folder and running npm install fixed it.

On Wed, Apr 26, 2017 at 4:20 AM, Peter Villeneuve <petervnv1@gmail.com> > wrote:
> Hi guys,
>
> Just did a fresh git clone and am having issues with webpack version.
> I installed nodejs 6 on ubuntu and after doing npm install I get unmet
> dependency for webpack
>
> ├── react-i18next@3.1.0
> └── UNMET PEER DEPENDENCY webpack@1.14.0
>
> Anyone else getting this error?
>
> Cheers
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#7

Hi,

Not sure why you get this error about BatchedBridge, its something
about configuring your dev environment/devices.
Java8, node LTS release 6.10.x.

Regards
damencho

···

On Thu, Apr 27, 2017 at 12:51 PM, Peter Villeneuve <petervnv1@gmail.com> wrote:

Thanks Damian,

Indeed deleting the node_modules folder and running npm install fixed it and
I can now compile the app.
However, as soon as it starts on my S6 running 7.0 I get the red screen
error:

"Could not get BatchedBridge, make sure your bundle is packaged correctly"

I'm using java-8-openjdk-amd64, node 7.9.0 and running npm 4.2.0.

I noticed during compilation a whole bunch of warnings regarding seemingly
out of date libraries.

What environment are you using that works well (ie what jdk, node, npm,
etc)?

Cheers,
Peter

On Wed, Apr 26, 2017 at 7:46 PM, Damian Minkov <damencho@jitsi.org> wrote:

I ran into the same issue today using node 6.10.x, deleting
node_modules folder and running npm install fixed it.

On Wed, Apr 26, 2017 at 4:20 AM, Peter Villeneuve <petervnv1@gmail.com> >> wrote:
> Hi guys,
>
> Just did a fresh git clone and am having issues with webpack version.
> I installed nodejs 6 on ubuntu and after doing npm install I get unmet
> dependency for webpack
>
> ├── react-i18next@3.1.0
> └── UNMET PEER DEPENDENCY webpack@1.14.0
>
> Anyone else getting this error?
>
> Cheers
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#8

Did you try the following?
1. Shake the phone or hit the menu button if available.
2. If the menu, select Dev Settings.
3. Select Debug server host & port for device.
4. Type the IP:port of the react-native packager. The default port is 8081.

···

On Thu, Apr 27, 2017 at 12:51 PM, Peter Villeneuve <petervnv1@gmail.com> wrote:

However, as soon as it starts on my S6 running 7.0 I get the red screen
error:

"Could not get BatchedBridge, make sure your bundle is packaged correctly"


#9

I tried what you said Lyubomir but it didn't work.
It seems to me that after running react-native run-android and pushing the
adb onto the phone, there is no packager listening on my machine.
Running netstat doesn't show anything listening on that port.

Anyway, I will try and compile again tomorrow, this time on my OSX machine
and will let you know.

···

On Thu, Apr 27, 2017 at 7:13 PM, Lyubomir Marinov < lyubomir.marinov@jitsi.org> wrote:

On Thu, Apr 27, 2017 at 12:51 PM, Peter Villeneuve <petervnv1@gmail.com> > wrote:
> However, as soon as it starts on my S6 running 7.0 I get the red screen
> error:
>
> "Could not get BatchedBridge, make sure your bundle is packaged
correctly"

Did you try the following?
1. Shake the phone or hit the menu button if available.
2. If the menu, select Dev Settings.
3. Select Debug server host & port for device.
4. Type the IP:port of the react-native packager. The default port is 8081.

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#10

1. Execute `react-native run-android` which installs the app. If
react-native packager is not running, the command will start it. It it
doesn't start it, there's probably a problem. You can start it
yourself with `react-native start`. Leave it open in the background.
2. Start the app and the red screen shows you the error.
3. Follow my instructions from my previous mail.
4. Shake/click menu again and do Reload.
5. The bundle should load from react-native packager.

···

On Thu, Apr 27, 2017 at 2:04 PM, Peter Villeneuve <petervnv1@gmail.com> wrote:

I tried what you said Lyubomir but it didn't work.
It seems to me that after running react-native run-android and pushing the
adb onto the phone, there is no packager listening on my machine.
Running netstat doesn't show anything listening on that port.


#11

Thanks Lyubomir.

I ended up compiling on my mac and it's working OK now.
Will keep testing.

Cheers

···

On Thu, Apr 27, 2017 at 8:23 PM, Lyubomir Marinov < lyubomir.marinov@jitsi.org> wrote:

On Thu, Apr 27, 2017 at 2:04 PM, Peter Villeneuve <petervnv1@gmail.com> > wrote:
> I tried what you said Lyubomir but it didn't work.
> It seems to me that after running react-native run-android and pushing
the
> adb onto the phone, there is no packager listening on my machine.
> Running netstat doesn't show anything listening on that port.

1. Execute `react-native run-android` which installs the app. If
react-native packager is not running, the command will start it. It it
doesn't start it, there's probably a problem. You can start it
yourself with `react-native start`. Leave it open in the background.
2. Start the app and the red screen shows you the error.
3. Follow my instructions from my previous mail.
4. Shake/click menu again and do Reload.
5. The bundle should load from react-native packager.

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#12

OK, I went back to try and compile on ubuntu/mint and when I run I get the
following errors and the packager doesn't start.

I'm running node v6.10.2, npm 4.5.0, JDK 8 on Mint 18.1 Serena

│ Running packager on port
8081. │


│ Keep this packager running while developing on any JS projects.
Feel │
│ free to close this tab and run your own packager instance if
you │

prefer. │


https://github.com/facebook/react-native



└────────────────────────────────────────────────────────────────────────────┘

Looking for JS files in
   /home/android_app/jitsi-meet

Loading dependency graph...
React packager ready.

jest-haste-map: @providesModule naming collision:
  Duplicate module name: escape-html
  Paths:
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/serve-index/node_modules/escape-html/package.json
collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/escape-html/package.json

This warning is caused by a @providesModule declaration with the same name
across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: debug
  Paths:
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/serve-index/node_modules/debug/package.json
collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/finalhandler/node_modules/debug/package.json

This warning is caused by a @providesModule declaration with the same name
across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: debug
  Paths:
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/connect/node_modules/debug/package.json
collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/serve-index/node_modules/debug/package.json

This warning is caused by a @providesModule declaration with the same name
across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: debug
  Paths:
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/body-parser/node_modules/debug/package.json
collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/connect/node_modules/debug/package.json

This warning is caused by a @providesModule declaration with the same name
across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: escape-html
  Paths:
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/send/node_modules/escape-html/package.json
collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/serve-index/node_modules/escape-html/package.json

This warning is caused by a @providesModule declaration with the same name
across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: debug
  Paths:
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/send/node_modules/debug/package.json
collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/body-parser/node_modules/debug/package.json

This warning is caused by a @providesModule declaration with the same name
across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: bytes
  Paths:
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/raw-body/node_modules/bytes/package.json
collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/bytes/package.json

This warning is caused by a @providesModule declaration with the same name
across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: iconv-lite
  Paths:
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/raw-body/node_modules/iconv-lite/package.json
collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/iconv-lite/package.json

This warning is caused by a @providesModule declaration with the same name
across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: depd
  Paths:
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/depd/package.json
collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/send/node_modules/depd/package.json

This warning is caused by a @providesModule declaration with the same name
across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: mime-types
  Paths:
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/mime-types/package.json
collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/type-is/node_modules/mime-types/package.json

This warning is caused by a @providesModule declaration with the same name
across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: escape-html
  Paths:
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/serve-static/node_modules/escape-html/package.json
collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/send/node_modules/escape-html/package.json

This warning is caused by a @providesModule declaration with the same name
across two different files.
ERROR watch
/home/android_app/jitsi-meet/android/app/build/intermediates/res/merged/release/values-de
ENOSPC
{"code":"ENOSPC","errno":"ENOSPC","syscall":"watch
/home/android_app/jitsi-meet/android/app/build/intermediates/res/merged/release/values-de","filename":"/home/android_app/jitsi-meet/android/app/build/intermediates/res/merged/release/values-de"}
Error: watch
/home/android_app/jitsi-meet/android/app/build/intermediates/res/merged/release/values-de
ENOSPC
    at exports._errnoException (util.js:1018:11)
    at FSWatcher.start (fs.js:1443:19)
    at Object.fs.watch (fs.js:1470:11)
    at NodeWatcher.watchdir
(/home/android_app/jitsi-meet/node_modules/sane/src/node_watcher.js:144:20)
    at Walker.<anonymous>
(/home/android_app/jitsi-meet/node_modules/sane/src/node_watcher.js:353:12)
    at emitTwo (events.js:106:13)
    at Walker.emit (events.js:191:7)
    at /home/android_app/jitsi-meet/node_modules/walker/lib/walker.js:69:16
    at go$readdir$cb
(/home/android_app/jitsi-meet/node_modules/graceful-fs/graceful-fs.js:149:14)
    at FSReqWrap.oncomplete (fs.js:123:15)

See http://facebook.github.io/react-native/docs/troubleshooting.html
for common problems and solutions.

···

On Thu, Apr 27, 2017 at 8:54 PM, Peter Villeneuve <petervnv1@gmail.com> wrote:

Thanks Lyubomir.

I ended up compiling on my mac and it's working OK now.
Will keep testing.

Cheers

On Thu, Apr 27, 2017 at 8:23 PM, Lyubomir Marinov < > lyubomir.marinov@jitsi.org> wrote:

On Thu, Apr 27, 2017 at 2:04 PM, Peter Villeneuve <petervnv1@gmail.com> >> wrote:
> I tried what you said Lyubomir but it didn't work.
> It seems to me that after running react-native run-android and pushing
the
> adb onto the phone, there is no packager listening on my machine.
> Running netstat doesn't show anything listening on that port.

1. Execute `react-native run-android` which installs the app. If
react-native packager is not running, the command will start it. It it
doesn't start it, there's probably a problem. You can start it
yourself with `react-native start`. Leave it open in the background.
2. Start the app and the red screen shows you the error.
3. Follow my instructions from my previous mail.
4. Shake/click menu again and do Reload.
5. The bundle should load from react-native packager.

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#13

Also, I'm running the correct react native version according to the
settings in package.json

react-native -v
react-native-cli: 2.0.1
react-native: 0.42.3

···

On Sat, Apr 29, 2017 at 6:45 PM, Peter Villeneuve <petervnv1@gmail.com> wrote:

OK, I went back to try and compile on ubuntu/mint and when I run I get the
following errors and the packager doesn't start.

I'm running node v6.10.2, npm 4.5.0, JDK 8 on Mint 18.1 Serena

│ Running packager on port 8081.



│ Keep this packager running while developing on any JS projects.
Feel │
│ free to close this tab and run your own packager instance if
you │
│ prefer.



https://github.com/facebook/react-native



└────────────────────────────────────────────────────────────────────────────┘

Looking for JS files in
   /home/android_app/jitsi-meet

Loading dependency graph...
React packager ready.

jest-haste-map: @providesModule naming collision:
  Duplicate module name: escape-html
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/serve-index/node_modules/escape-html/package.json collides
with /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/escape-html/package.json

This warning is caused by a @providesModule declaration with the same name
across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: debug
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/serve-index/node_modules/debug/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/
node_modules/finalhandler/node_modules/debug/package.json

This warning is caused by a @providesModule declaration with the same name
across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: debug
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/connect/node_modules/debug/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/
node_modules/serve-index/node_modules/debug/package.json

This warning is caused by a @providesModule declaration with the same name
across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: debug
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/body-parser/node_modules/debug/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/
node_modules/connect/node_modules/debug/package.json

This warning is caused by a @providesModule declaration with the same name
across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: escape-html
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/send/node_modules/escape-html/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/
node_modules/serve-index/node_modules/escape-html/package.json

This warning is caused by a @providesModule declaration with the same name
across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: debug
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/send/node_modules/debug/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/
node_modules/body-parser/node_modules/debug/package.json

This warning is caused by a @providesModule declaration with the same name
across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: bytes
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/raw-body/node_modules/bytes/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/
node_modules/bytes/package.json

This warning is caused by a @providesModule declaration with the same name
across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: iconv-lite
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/raw-body/node_modules/iconv-lite/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/
node_modules/iconv-lite/package.json

This warning is caused by a @providesModule declaration with the same name
across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: depd
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_modules/depd/package.json
collides with /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/send/node_modules/depd/package.json

This warning is caused by a @providesModule declaration with the same name
across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: mime-types
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/mime-types/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/
node_modules/type-is/node_modules/mime-types/package.json

This warning is caused by a @providesModule declaration with the same name
across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: escape-html
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/serve-static/node_modules/escape-html/package.json collides
with /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/send/node_modules/escape-html/package.json

This warning is caused by a @providesModule declaration with the same name
across two different files.
ERROR watch /home/android_app/jitsi-meet/android/app/build/
intermediates/res/merged/release/values-de ENOSPC
{"code":"ENOSPC","errno":"ENOSPC","syscall":"watch
/home/android_app/jitsi-meet/android/app/build/intermediates/res/merged/
release/values-de","filename":"/home/android_app/jitsi-meet/
android/app/build/intermediates/res/merged/release/values-de"}
Error: watch /home/android_app/jitsi-meet/android/app/build/
intermediates/res/merged/release/values-de ENOSPC
    at exports._errnoException (util.js:1018:11)
    at FSWatcher.start (fs.js:1443:19)
    at Object.fs.watch (fs.js:1470:11)
    at NodeWatcher.watchdir (/home/android_app/jitsi-meet/
node_modules/sane/src/node_watcher.js:144:20)
    at Walker.<anonymous> (/home/android_app/jitsi-meet/
node_modules/sane/src/node_watcher.js:353:12)
    at emitTwo (events.js:106:13)
    at Walker.emit (events.js:191:7)
    at /home/android_app/jitsi-meet/node_modules/walker/lib/
walker.js:69:16
    at go$readdir$cb (/home/android_app/jitsi-meet/
node_modules/graceful-fs/graceful-fs.js:149:14)
    at FSReqWrap.oncomplete (fs.js:123:15)

See http://facebook.github.io/react-native/docs/troubleshooting.html
for common problems and solutions.

On Thu, Apr 27, 2017 at 8:54 PM, Peter Villeneuve <petervnv1@gmail.com> > wrote:

Thanks Lyubomir.

I ended up compiling on my mac and it's working OK now.
Will keep testing.

Cheers

On Thu, Apr 27, 2017 at 8:23 PM, Lyubomir Marinov < >> lyubomir.marinov@jitsi.org> wrote:

On Thu, Apr 27, 2017 at 2:04 PM, Peter Villeneuve <petervnv1@gmail.com> >>> wrote:
> I tried what you said Lyubomir but it didn't work.
> It seems to me that after running react-native run-android and pushing
the
> adb onto the phone, there is no packager listening on my machine.
> Running netstat doesn't show anything listening on that port.

1. Execute `react-native run-android` which installs the app. If
react-native packager is not running, the command will start it. It it
doesn't start it, there's probably a problem. You can start it
yourself with `react-native start`. Leave it open in the background.
2. Start the app and the red screen shows you the error.
3. Follow my instructions from my previous mail.
4. Shake/click menu again and do Reload.
5. The bundle should load from react-native packager.

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#14

I also got these warnings

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0
(node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for
fsevents@1.1.1: wanted {"os":"darwin","arch":"any"} (current:
{"os":"linux","arch":"x64"})
npm WARN eslint-plugin-mocha@2.0.0 requires a peer of eslint@^2.0.0 but
none was installed.
npm WARN babel-loader@7.0.0 requires a peer of webpack@2 but none was
installed.

···

On Sat, Apr 29, 2017 at 6:55 PM, Peter Villeneuve <petervnv1@gmail.com> wrote:

Also, I'm running the correct react native version according to the
settings in package.json

react-native -v
react-native-cli: 2.0.1
react-native: 0.42.3

On Sat, Apr 29, 2017 at 6:45 PM, Peter Villeneuve <petervnv1@gmail.com> > wrote:

OK, I went back to try and compile on ubuntu/mint and when I run I get
the following errors and the packager doesn't start.

I'm running node v6.10.2, npm 4.5.0, JDK 8 on Mint 18.1 Serena

│ Running packager on port 8081.



│ Keep this packager running while developing on any JS projects.
Feel │
│ free to close this tab and run your own packager instance if
you │
│ prefer.



https://github.com/facebook/react-native



└────────────────────────────────────────────────────────────────────────────┘

Looking for JS files in
   /home/android_app/jitsi-meet

Loading dependency graph...
React packager ready.

jest-haste-map: @providesModule naming collision:
  Duplicate module name: escape-html
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/serve-index/node_modules/escape-html/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_
modules/escape-html/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: debug
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/serve-index/node_modules/debug/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_
modules/finalhandler/node_modules/debug/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: debug
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/connect/node_modules/debug/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_
modules/serve-index/node_modules/debug/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: debug
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/body-parser/node_modules/debug/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_
modules/connect/node_modules/debug/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: escape-html
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/send/node_modules/escape-html/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_
modules/serve-index/node_modules/escape-html/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: debug
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/send/node_modules/debug/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_
modules/body-parser/node_modules/debug/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: bytes
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/raw-body/node_modules/bytes/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_
modules/bytes/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: iconv-lite
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/raw-body/node_modules/iconv-lite/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_
modules/iconv-lite/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: depd
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_modules/depd/package.json
collides with /home/android_app/jitsi-meet/n
ode_modules/react-native/node_modules/send/node_modules/depd/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: mime-types
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/mime-types/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_
modules/type-is/node_modules/mime-types/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: escape-html
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/serve-static/node_modules/escape-html/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_
modules/send/node_modules/escape-html/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
ERROR watch /home/android_app/jitsi-meet/a
ndroid/app/build/intermediates/res/merged/release/values-de ENOSPC
{"code":"ENOSPC","errno":"ENOSPC","syscall":"watch
/home/android_app/jitsi-meet/android/app/build/intermediates
/res/merged/release/values-de","filename":"/home/android_
app/jitsi-meet/android/app/build/intermediates/res/
merged/release/values-de"}
Error: watch /home/android_app/jitsi-meet/android/app/build/intermediates/res/merged/release/values-de
ENOSPC
    at exports._errnoException (util.js:1018:11)
    at FSWatcher.start (fs.js:1443:19)
    at Object.fs.watch (fs.js:1470:11)
    at NodeWatcher.watchdir (/home/android_app/jitsi-meet/
node_modules/sane/src/node_watcher.js:144:20)
    at Walker.<anonymous> (/home/android_app/jitsi-meet/
node_modules/sane/src/node_watcher.js:353:12)
    at emitTwo (events.js:106:13)
    at Walker.emit (events.js:191:7)
    at /home/android_app/jitsi-meet/node_modules/walker/lib/walker.
js:69:16
    at go$readdir$cb (/home/android_app/jitsi-meet/
node_modules/graceful-fs/graceful-fs.js:149:14)
    at FSReqWrap.oncomplete (fs.js:123:15)

See http://facebook.github.io/react-native/docs/troubleshooting.html
for common problems and solutions.

On Thu, Apr 27, 2017 at 8:54 PM, Peter Villeneuve <petervnv1@gmail.com> >> wrote:

Thanks Lyubomir.

I ended up compiling on my mac and it's working OK now.
Will keep testing.

Cheers

On Thu, Apr 27, 2017 at 8:23 PM, Lyubomir Marinov < >>> lyubomir.marinov@jitsi.org> wrote:

On Thu, Apr 27, 2017 at 2:04 PM, Peter Villeneuve <petervnv1@gmail.com> >>>> wrote:
> I tried what you said Lyubomir but it didn't work.
> It seems to me that after running react-native run-android and
pushing the
> adb onto the phone, there is no packager listening on my machine.
> Running netstat doesn't show anything listening on that port.

1. Execute `react-native run-android` which installs the app. If
react-native packager is not running, the command will start it. It it
doesn't start it, there's probably a problem. You can start it
yourself with `react-native start`. Leave it open in the background.
2. Start the app and the red screen shows you the error.
3. Follow my instructions from my previous mail.
4. Shake/click menu again and do Reload.
5. The bundle should load from react-native packager.

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#15

I'm now back at my OS X machine and I'm getting the annoying BatchedBridge
error
again.

I think the problem lies with the @providesModule naming collisions
referenced above.

Is anyone else experiencing these problems? If so, any solutions or
workarounds?

Cheers,
Peter

···

On Sat, Apr 29, 2017 at 8:28 PM, Peter Villeneuve <petervnv1@gmail.com> wrote:

I also got these warnings

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0
(node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for
fsevents@1.1.1: wanted {"os":"darwin","arch":"any"} (current:
{"os":"linux","arch":"x64"})
npm WARN eslint-plugin-mocha@2.0.0 requires a peer of eslint@^2.0.0 but
none was installed.
npm WARN babel-loader@7.0.0 requires a peer of webpack@2 but none was
installed.

On Sat, Apr 29, 2017 at 6:55 PM, Peter Villeneuve <petervnv1@gmail.com> > wrote:

Also, I'm running the correct react native version according to the
settings in package.json

react-native -v
react-native-cli: 2.0.1
react-native: 0.42.3

On Sat, Apr 29, 2017 at 6:45 PM, Peter Villeneuve <petervnv1@gmail.com> >> wrote:

OK, I went back to try and compile on ubuntu/mint and when I run I get
the following errors and the packager doesn't start.

I'm running node v6.10.2, npm 4.5.0, JDK 8 on Mint 18.1 Serena

│ Running packager on port 8081.



│ Keep this packager running while developing on any JS projects.
Feel │
│ free to close this tab and run your own packager instance if
you │
│ prefer.



https://github.com/facebook/react-native



└────────────────────────────────────────────────────────────────────────────┘

Looking for JS files in
   /home/android_app/jitsi-meet

Loading dependency graph...
React packager ready.

jest-haste-map: @providesModule naming collision:
  Duplicate module name: escape-html
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/serve-index/node_modules/escape-html/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_
modules/escape-html/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: debug
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/serve-index/node_modules/debug/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_
modules/finalhandler/node_modules/debug/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: debug
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/connect/node_modules/debug/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_
modules/serve-index/node_modules/debug/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: debug
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/body-parser/node_modules/debug/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_
modules/connect/node_modules/debug/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: escape-html
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/send/node_modules/escape-html/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_
modules/serve-index/node_modules/escape-html/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: debug
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/send/node_modules/debug/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_
modules/body-parser/node_modules/debug/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: bytes
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/raw-body/node_modules/bytes/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_
modules/bytes/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: iconv-lite
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/raw-body/node_modules/iconv-lite/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_
modules/iconv-lite/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: depd
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_modules/depd/package.json
collides with /home/android_app/jitsi-meet/n
ode_modules/react-native/node_modules/send/node_modules/depd
/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: mime-types
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/mime-types/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_
modules/type-is/node_modules/mime-types/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: escape-html
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/serve-static/node_modules/escape-html/package.json collides
with /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/send/node_modules/escape-html/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
ERROR watch /home/android_app/jitsi-meet/a
ndroid/app/build/intermediates/res/merged/release/values-de ENOSPC
{"code":"ENOSPC","errno":"ENOSPC","syscall":"watch
/home/android_app/jitsi-meet/android/app/build/intermediates
/res/merged/release/values-de","filename":"/home/android_app
/jitsi-meet/android/app/build/intermediates/res/merged/
release/values-de"}
Error: watch /home/android_app/jitsi-meet/a
ndroid/app/build/intermediates/res/merged/release/values-de ENOSPC
    at exports._errnoException (util.js:1018:11)
    at FSWatcher.start (fs.js:1443:19)
    at Object.fs.watch (fs.js:1470:11)
    at NodeWatcher.watchdir (/home/android_app/jitsi-meet/
node_modules/sane/src/node_watcher.js:144:20)
    at Walker.<anonymous> (/home/android_app/jitsi-meet/
node_modules/sane/src/node_watcher.js:353:12)
    at emitTwo (events.js:106:13)
    at Walker.emit (events.js:191:7)
    at /home/android_app/jitsi-meet/node_modules/walker/lib/walker.
js:69:16
    at go$readdir$cb (/home/android_app/jitsi-meet/
node_modules/graceful-fs/graceful-fs.js:149:14)
    at FSReqWrap.oncomplete (fs.js:123:15)

See http://facebook.github.io/react-native/docs/troubleshooting.html
for common problems and solutions.

On Thu, Apr 27, 2017 at 8:54 PM, Peter Villeneuve <petervnv1@gmail.com> >>> wrote:

Thanks Lyubomir.

I ended up compiling on my mac and it's working OK now.
Will keep testing.

Cheers

On Thu, Apr 27, 2017 at 8:23 PM, Lyubomir Marinov < >>>> lyubomir.marinov@jitsi.org> wrote:

On Thu, Apr 27, 2017 at 2:04 PM, Peter Villeneuve <petervnv1@gmail.com> >>>>> wrote:
> I tried what you said Lyubomir but it didn't work.
> It seems to me that after running react-native run-android and
pushing the
> adb onto the phone, there is no packager listening on my machine.
> Running netstat doesn't show anything listening on that port.

1. Execute `react-native run-android` which installs the app. If
react-native packager is not running, the command will start it. It it
doesn't start it, there's probably a problem. You can start it
yourself with `react-native start`. Leave it open in the background.
2. Start the app and the red screen shows you the error.
3. Follow my instructions from my previous mail.
4. Shake/click menu again and do Reload.
5. The bundle should load from react-native packager.

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#16

I just tried compiling a release version on both Mint and OSX and both
failed with these errors:

This warning is caused by a @providesModule declaration with the same name
across two different files.
Loading dependency graph, done.
warning: the transform cache was reset.

Unable to resolve module `uid` from
`/home/user/android/jitsi-meet/node_modules/@atlaskit/dropdown-menu/dist/bundle.js`:
Module does not exist in the module map or in these directories:

/home/user/android/jitsi-meet/node_modules/@atlaskit/dropdown-menu/node_modules
, /home/user/android/jitsi-meet/node_modules

This might be related to
https://github.com/facebook/react-native/issues/4968
To resolve try the following:
  1. Clear watchman watches: `watchman watch-del-all`.
  2. Delete the `node_modules` folder: `rm -rf node_modules && npm install`.
  3. Reset packager cache: `rm -fr $TMPDIR/react-*` or `npm start
--reset-cache`.

:app:bundleReleaseJsAndAssets FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:bundleReleaseJsAndAssets'.

Process 'command 'node'' finished with non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or
--debug option to get more log output.

BUILD FAILED

I did as instructed above (1, 2 and 3) but unfortunately it still doesn't
work.
It seems I'm not the only one with these RN errors, as can be seen here
<https://github.com/facebook/react-native/issues/10412> and here
<https://github.com/aksonov/react-native-router-flux/issues/1803>

has anyone else tried to build a release version of jitsi-meet for android?
Any ideas?

Cheers,
Peter

···

On Mon, May 1, 2017 at 2:46 PM, Peter Villeneuve <petervnv1@gmail.com> wrote:

I'm now back at my OS X machine and I'm getting the annoying BatchedBridge
error
again.

I think the problem lies with the @providesModule naming collisions
referenced above.

Is anyone else experiencing these problems? If so, any solutions or
workarounds?

Cheers,
Peter

On Sat, Apr 29, 2017 at 8:28 PM, Peter Villeneuve <petervnv1@gmail.com> > wrote:

I also got these warnings

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0
(node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for
fsevents@1.1.1: wanted {"os":"darwin","arch":"any"} (current:
{"os":"linux","arch":"x64"})
npm WARN eslint-plugin-mocha@2.0.0 requires a peer of eslint@^2.0.0 but
none was installed.
npm WARN babel-loader@7.0.0 requires a peer of webpack@2 but none was
installed.

On Sat, Apr 29, 2017 at 6:55 PM, Peter Villeneuve <petervnv1@gmail.com> >> wrote:

Also, I'm running the correct react native version according to the
settings in package.json

react-native -v
react-native-cli: 2.0.1
react-native: 0.42.3

On Sat, Apr 29, 2017 at 6:45 PM, Peter Villeneuve <petervnv1@gmail.com> >>> wrote:

OK, I went back to try and compile on ubuntu/mint and when I run I get
the following errors and the packager doesn't start.

I'm running node v6.10.2, npm 4.5.0, JDK 8 on Mint 18.1 Serena

│ Running packager on port 8081.



│ Keep this packager running while developing on any JS projects.
Feel │
│ free to close this tab and run your own packager instance if
you │
│ prefer.



https://github.com/facebook/react-native



└────────────────────────────────────────────────────────────────────────────┘

Looking for JS files in
   /home/android_app/jitsi-meet

Loading dependency graph...
React packager ready.

jest-haste-map: @providesModule naming collision:
  Duplicate module name: escape-html
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/serve-index/node_modules/escape-html/package.json collides
with /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/escape-html/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: debug
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/serve-index/node_modules/debug/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_
modules/finalhandler/node_modules/debug/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: debug
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/connect/node_modules/debug/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_
modules/serve-index/node_modules/debug/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: debug
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/body-parser/node_modules/debug/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_
modules/connect/node_modules/debug/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: escape-html
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/send/node_modules/escape-html/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_
modules/serve-index/node_modules/escape-html/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: debug
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/send/node_modules/debug/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_
modules/body-parser/node_modules/debug/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: bytes
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/raw-body/node_modules/bytes/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_
modules/bytes/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: iconv-lite
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/raw-body/node_modules/iconv-lite/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_
modules/iconv-lite/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: depd
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_modules/depd/package.json
collides with /home/android_app/jitsi-meet/n
ode_modules/react-native/node_modules/send/node_modules/depd
/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: mime-types
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/mime-types/package.json collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_
modules/type-is/node_modules/mime-types/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: escape-html
  Paths: /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/serve-static/node_modules/escape-html/package.json collides
with /home/android_app/jitsi-meet/node_modules/react-native/node_
modules/send/node_modules/escape-html/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
ERROR watch /home/android_app/jitsi-meet/a
ndroid/app/build/intermediates/res/merged/release/values-de ENOSPC
{"code":"ENOSPC","errno":"ENOSPC","syscall":"watch
/home/android_app/jitsi-meet/android/app/build/intermediates
/res/merged/release/values-de","filename":"/home/android_app
/jitsi-meet/android/app/build/intermediates/res/merged/relea
se/values-de"}
Error: watch /home/android_app/jitsi-meet/a
ndroid/app/build/intermediates/res/merged/release/values-de ENOSPC
    at exports._errnoException (util.js:1018:11)
    at FSWatcher.start (fs.js:1443:19)
    at Object.fs.watch (fs.js:1470:11)
    at NodeWatcher.watchdir (/home/android_app/jitsi-meet/
node_modules/sane/src/node_watcher.js:144:20)
    at Walker.<anonymous> (/home/android_app/jitsi-meet/
node_modules/sane/src/node_watcher.js:353:12)
    at emitTwo (events.js:106:13)
    at Walker.emit (events.js:191:7)
    at /home/android_app/jitsi-meet/node_modules/walker/lib/walker.
js:69:16
    at go$readdir$cb (/home/android_app/jitsi-meet/
node_modules/graceful-fs/graceful-fs.js:149:14)
    at FSReqWrap.oncomplete (fs.js:123:15)

See http://facebook.github.io/react-native/docs/troubleshooting.html
for common problems and solutions.

On Thu, Apr 27, 2017 at 8:54 PM, Peter Villeneuve <petervnv1@gmail.com> >>>> wrote:

Thanks Lyubomir.

I ended up compiling on my mac and it's working OK now.
Will keep testing.

Cheers

On Thu, Apr 27, 2017 at 8:23 PM, Lyubomir Marinov < >>>>> lyubomir.marinov@jitsi.org> wrote:

On Thu, Apr 27, 2017 at 2:04 PM, Peter Villeneuve < >>>>>> petervnv1@gmail.com> wrote:
> I tried what you said Lyubomir but it didn't work.
> It seems to me that after running react-native run-android and
pushing the
> adb onto the phone, there is no packager listening on my machine.
> Running netstat doesn't show anything listening on that port.

1. Execute `react-native run-android` which installs the app. If
react-native packager is not running, the command will start it. It it
doesn't start it, there's probably a problem. You can start it
yourself with `react-native start`. Leave it open in the background.
2. Start the app and the red screen shows you the error.
3. Follow my instructions from my previous mail.
4. Shake/click menu again and do Reload.
5. The bundle should load from react-native packager.

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#17

Hi,

Yes, this is a known issue which was introduced in a commit yesterday.
There is already a PR fixing this:
https://github.com/jitsi/jitsi-meet/pull/1545. We will most probably
merge it today.

Regards
damencho

···

On Tue, May 2, 2017 at 7:36 AM, Peter Villeneuve <petervnv1@gmail.com> wrote:

I just tried compiling a release version on both Mint and OSX and both
failed with these errors:

This warning is caused by a @providesModule declaration with the same name
across two different files.
Loading dependency graph, done.
warning: the transform cache was reset.

Unable to resolve module `uid` from
`/home/user/android/jitsi-meet/node_modules/@atlaskit/dropdown-menu/dist/bundle.js`:
Module does not exist in the module map or in these directories:

/home/user/android/jitsi-meet/node_modules/@atlaskit/dropdown-menu/node_modules
, /home/user/android/jitsi-meet/node_modules

This might be related to
https://github.com/facebook/react-native/issues/4968
To resolve try the following:
  1. Clear watchman watches: `watchman watch-del-all`.
  2. Delete the `node_modules` folder: `rm -rf node_modules && npm install`.
  3. Reset packager cache: `rm -fr $TMPDIR/react-*` or `npm start
--reset-cache`.

:app:bundleReleaseJsAndAssets FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:bundleReleaseJsAndAssets'.

Process 'command 'node'' finished with non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or
--debug option to get more log output.

BUILD FAILED

I did as instructed above (1, 2 and 3) but unfortunately it still doesn't
work.
It seems I'm not the only one with these RN errors, as can be seen here and
here

has anyone else tried to build a release version of jitsi-meet for android?
Any ideas?

Cheers,
Peter

On Mon, May 1, 2017 at 2:46 PM, Peter Villeneuve <petervnv1@gmail.com> > wrote:

I'm now back at my OS X machine and I'm getting the annoying BatchedBridge
error
again.

I think the problem lies with the @providesModule naming collisions
referenced above.

Is anyone else experiencing these problems? If so, any solutions or
workarounds?

Cheers,
Peter

On Sat, Apr 29, 2017 at 8:28 PM, Peter Villeneuve <petervnv1@gmail.com> >> wrote:

I also got these warnings

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0
(node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for
fsevents@1.1.1: wanted {"os":"darwin","arch":"any"} (current:
{"os":"linux","arch":"x64"})
npm WARN eslint-plugin-mocha@2.0.0 requires a peer of eslint@^2.0.0 but
none was installed.
npm WARN babel-loader@7.0.0 requires a peer of webpack@2 but none was
installed.

On Sat, Apr 29, 2017 at 6:55 PM, Peter Villeneuve <petervnv1@gmail.com> >>> wrote:

Also, I'm running the correct react native version according to the
settings in package.json

react-native -v
react-native-cli: 2.0.1
react-native: 0.42.3

On Sat, Apr 29, 2017 at 6:45 PM, Peter Villeneuve <petervnv1@gmail.com> >>>> wrote:

OK, I went back to try and compile on ubuntu/mint and when I run I get
the following errors and the packager doesn't start.

I'm running node v6.10.2, npm 4.5.0, JDK 8 on Mint 18.1 Serena

│ Running packager on port 8081.



│ Keep this packager running while developing on any JS projects.
Feel │
│ free to close this tab and run your own packager instance if you

│ prefer.



https://github.com/facebook/react-native


└────────────────────────────────────────────────────────────────────────────┘
Looking for JS files in
   /home/android_app/jitsi-meet

Loading dependency graph...
React packager ready.

jest-haste-map: @providesModule naming collision:
  Duplicate module name: escape-html
  Paths:
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/serve-index/node_modules/escape-html/package.json
collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/escape-html/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: debug
  Paths:
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/serve-index/node_modules/debug/package.json
collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/finalhandler/node_modules/debug/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: debug
  Paths:
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/connect/node_modules/debug/package.json
collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/serve-index/node_modules/debug/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: debug
  Paths:
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/body-parser/node_modules/debug/package.json
collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/connect/node_modules/debug/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: escape-html
  Paths:
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/send/node_modules/escape-html/package.json
collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/serve-index/node_modules/escape-html/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: debug
  Paths:
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/send/node_modules/debug/package.json
collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/body-parser/node_modules/debug/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: bytes
  Paths:
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/raw-body/node_modules/bytes/package.json
collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/bytes/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: iconv-lite
  Paths:
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/raw-body/node_modules/iconv-lite/package.json
collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/iconv-lite/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: depd
  Paths:
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/depd/package.json
collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/send/node_modules/depd/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: mime-types
  Paths:
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/mime-types/package.json
collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/type-is/node_modules/mime-types/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: escape-html
  Paths:
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/serve-static/node_modules/escape-html/package.json
collides with
/home/android_app/jitsi-meet/node_modules/react-native/node_modules/send/node_modules/escape-html/package.json

This warning is caused by a @providesModule declaration with the same
name across two different files.
ERROR watch
/home/android_app/jitsi-meet/android/app/build/intermediates/res/merged/release/values-de
ENOSPC
{"code":"ENOSPC","errno":"ENOSPC","syscall":"watch
/home/android_app/jitsi-meet/android/app/build/intermediates/res/merged/release/values-de","filename":"/home/android_app/jitsi-meet/android/app/build/intermediates/res/merged/release/values-de"}
Error: watch
/home/android_app/jitsi-meet/android/app/build/intermediates/res/merged/release/values-de
ENOSPC
    at exports._errnoException (util.js:1018:11)
    at FSWatcher.start (fs.js:1443:19)
    at Object.fs.watch (fs.js:1470:11)
    at NodeWatcher.watchdir
(/home/android_app/jitsi-meet/node_modules/sane/src/node_watcher.js:144:20)
    at Walker.<anonymous>
(/home/android_app/jitsi-meet/node_modules/sane/src/node_watcher.js:353:12)
    at emitTwo (events.js:106:13)
    at Walker.emit (events.js:191:7)
    at
/home/android_app/jitsi-meet/node_modules/walker/lib/walker.js:69:16
    at go$readdir$cb
(/home/android_app/jitsi-meet/node_modules/graceful-fs/graceful-fs.js:149:14)
    at FSReqWrap.oncomplete (fs.js:123:15)

See http://facebook.github.io/react-native/docs/troubleshooting.html
for common problems and solutions.

On Thu, Apr 27, 2017 at 8:54 PM, Peter Villeneuve <petervnv1@gmail.com> >>>>> wrote:

Thanks Lyubomir.

I ended up compiling on my mac and it's working OK now.
Will keep testing.

Cheers

On Thu, Apr 27, 2017 at 8:23 PM, Lyubomir Marinov >>>>>> <lyubomir.marinov@jitsi.org> wrote:

On Thu, Apr 27, 2017 at 2:04 PM, Peter Villeneuve >>>>>>> <petervnv1@gmail.com> wrote:
> I tried what you said Lyubomir but it didn't work.
> It seems to me that after running react-native run-android and
> pushing the
> adb onto the phone, there is no packager listening on my machine.
> Running netstat doesn't show anything listening on that port.

1. Execute `react-native run-android` which installs the app. If
react-native packager is not running, the command will start it. It
it
doesn't start it, there's probably a problem. You can start it
yourself with `react-native start`. Leave it open in the background.
2. Start the app and the red screen shows you the error.
3. Follow my instructions from my previous mail.
4. Shake/click menu again and do Reload.
5. The bundle should load from react-native packager.

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#18

Thanks Damian.
I was ready to pull my hair out :wink:

···

On Tue, May 2, 2017 at 3:58 PM, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

Yes, this is a known issue which was introduced in a commit yesterday.
There is already a PR fixing this:
https://github.com/jitsi/jitsi-meet/pull/1545. We will most probably
merge it today.

Regards
damencho

On Tue, May 2, 2017 at 7:36 AM, Peter Villeneuve <petervnv1@gmail.com> > wrote:
> I just tried compiling a release version on both Mint and OSX and both
> failed with these errors:
>
> This warning is caused by a @providesModule declaration with the same
name
> across two different files.
> Loading dependency graph, done.
> warning: the transform cache was reset.
>
> Unable to resolve module `uid` from
> `/home/user/android/jitsi-meet/node_modules/@atlaskit/
dropdown-menu/dist/bundle.js`:
> Module does not exist in the module map or in these directories:
>
> /home/user/android/jitsi-meet/node_modules/@atlaskit/
dropdown-menu/node_modules
> , /home/user/android/jitsi-meet/node_modules
>
> This might be related to
> https://github.com/facebook/react-native/issues/4968
> To resolve try the following:
> 1. Clear watchman watches: `watchman watch-del-all`.
> 2. Delete the `node_modules` folder: `rm -rf node_modules && npm
install`.
> 3. Reset packager cache: `rm -fr $TMPDIR/react-*` or `npm start
> --reset-cache`.
>
> :app:bundleReleaseJsAndAssets FAILED
>
> FAILURE: Build failed with an exception.
>
> * What went wrong:
> Execution failed for task ':app:bundleReleaseJsAndAssets'.
>> Process 'command 'node'' finished with non-zero exit value 1
>
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output.
>
> BUILD FAILED
>
>
> I did as instructed above (1, 2 and 3) but unfortunately it still doesn't
> work.
> It seems I'm not the only one with these RN errors, as can be seen here
and
> here
>
> has anyone else tried to build a release version of jitsi-meet for
android?
> Any ideas?
>
>
> Cheers,
> Peter
>
>
>
> On Mon, May 1, 2017 at 2:46 PM, Peter Villeneuve <petervnv1@gmail.com> > > wrote:
>>
>> I'm now back at my OS X machine and I'm getting the annoying
BatchedBridge
>> error
>> again.
>>
>> I think the problem lies with the @providesModule naming collisions
>> referenced above.
>>
>> Is anyone else experiencing these problems? If so, any solutions or
>> workarounds?
>>
>> Cheers,
>> Peter
>>
>> On Sat, Apr 29, 2017 at 8:28 PM, Peter Villeneuve <petervnv1@gmail.com> > >> wrote:
>>>
>>> I also got these warnings
>>>
>>> npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0
>>> (node_modules/chokidar/node_modules/fsevents):
>>> npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for
>>> fsevents@1.1.1: wanted {"os":"darwin","arch":"any"} (current:
>>> {"os":"linux","arch":"x64"})
>>> npm WARN eslint-plugin-mocha@2.0.0 requires a peer of eslint@^2.0.0
but
>>> none was installed.
>>> npm WARN babel-loader@7.0.0 requires a peer of webpack@2 but none was
>>> installed.
>>>
>>> On Sat, Apr 29, 2017 at 6:55 PM, Peter Villeneuve <petervnv1@gmail.com > > > >>> wrote:
>>>>
>>>> Also, I'm running the correct react native version according to the
>>>> settings in package.json
>>>>
>>>> react-native -v
>>>> react-native-cli: 2.0.1
>>>> react-native: 0.42.3
>>>>
>>>>
>>>> On Sat, Apr 29, 2017 at 6:45 PM, Peter Villeneuve < > petervnv1@gmail.com> > >>>> wrote:
>>>>>
>>>>> OK, I went back to try and compile on ubuntu/mint and when I run I
get
>>>>> the following errors and the packager doesn't start.
>>>>>
>>>>> I'm running node v6.10.2, npm 4.5.0, JDK 8 on Mint 18.1 Serena
>>>>>
>>>>>
>>>>> │ Running packager on port 8081.
>>>>> │
>>>>> │
>>>>> │
>>>>> │ Keep this packager running while developing on any JS projects.
>>>>> Feel │
>>>>> │ free to close this tab and run your own packager instance if you
>>>>> │
>>>>> │ prefer.
>>>>> │
>>>>> │
>>>>> │
>>>>> │ https://github.com/facebook/react-native
>>>>> │
>>>>> │
>>>>> │
>>>>>
>>>>> └───────────────────────────────────────────────────────────
─────────────────┘
>>>>> Looking for JS files in
>>>>> /home/android_app/jitsi-meet
>>>>>
>>>>> Loading dependency graph...
>>>>> React packager ready.
>>>>>
>>>>> jest-haste-map: @providesModule naming collision:
>>>>> Duplicate module name: escape-html
>>>>> Paths:
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/serve-index/node_modules/escape-html/package.json
>>>>> collides with
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/escape-html/package.json
>>>>>
>>>>> This warning is caused by a @providesModule declaration with the same
>>>>> name across two different files.
>>>>> jest-haste-map: @providesModule naming collision:
>>>>> Duplicate module name: debug
>>>>> Paths:
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/serve-index/node_modules/debug/package.json
>>>>> collides with
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/finalhandler/node_modules/debug/package.json
>>>>>
>>>>> This warning is caused by a @providesModule declaration with the same
>>>>> name across two different files.
>>>>> jest-haste-map: @providesModule naming collision:
>>>>> Duplicate module name: debug
>>>>> Paths:
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/connect/node_modules/debug/package.json
>>>>> collides with
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/serve-index/node_modules/debug/package.json
>>>>>
>>>>> This warning is caused by a @providesModule declaration with the same
>>>>> name across two different files.
>>>>> jest-haste-map: @providesModule naming collision:
>>>>> Duplicate module name: debug
>>>>> Paths:
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/body-parser/node_modules/debug/package.json
>>>>> collides with
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/connect/node_modules/debug/package.json
>>>>>
>>>>> This warning is caused by a @providesModule declaration with the same
>>>>> name across two different files.
>>>>> jest-haste-map: @providesModule naming collision:
>>>>> Duplicate module name: escape-html
>>>>> Paths:
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/send/node_modules/escape-html/package.json
>>>>> collides with
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/serve-index/node_modules/escape-html/package.json
>>>>>
>>>>> This warning is caused by a @providesModule declaration with the same
>>>>> name across two different files.
>>>>> jest-haste-map: @providesModule naming collision:
>>>>> Duplicate module name: debug
>>>>> Paths:
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/send/node_modules/debug/package.json
>>>>> collides with
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/body-parser/node_modules/debug/package.json
>>>>>
>>>>> This warning is caused by a @providesModule declaration with the same
>>>>> name across two different files.
>>>>> jest-haste-map: @providesModule naming collision:
>>>>> Duplicate module name: bytes
>>>>> Paths:
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/raw-body/node_modules/bytes/package.json
>>>>> collides with
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/bytes/package.json
>>>>>
>>>>> This warning is caused by a @providesModule declaration with the same
>>>>> name across two different files.
>>>>> jest-haste-map: @providesModule naming collision:
>>>>> Duplicate module name: iconv-lite
>>>>> Paths:
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/raw-body/node_modules/iconv-lite/package.json
>>>>> collides with
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/iconv-lite/package.json
>>>>>
>>>>> This warning is caused by a @providesModule declaration with the same
>>>>> name across two different files.
>>>>> jest-haste-map: @providesModule naming collision:
>>>>> Duplicate module name: depd
>>>>> Paths:
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/depd/package.json
>>>>> collides with
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/send/node_modules/depd/package.json
>>>>>
>>>>> This warning is caused by a @providesModule declaration with the same
>>>>> name across two different files.
>>>>> jest-haste-map: @providesModule naming collision:
>>>>> Duplicate module name: mime-types
>>>>> Paths:
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/mime-types/package.json
>>>>> collides with
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/type-is/node_modules/mime-types/package.json
>>>>>
>>>>> This warning is caused by a @providesModule declaration with the same
>>>>> name across two different files.
>>>>> jest-haste-map: @providesModule naming collision:
>>>>> Duplicate module name: escape-html
>>>>> Paths:
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/serve-static/node_modules/escape-html/package.json
>>>>> collides with
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/send/node_modules/escape-html/package.json
>>>>>
>>>>> This warning is caused by a @providesModule declaration with the same
>>>>> name across two different files.
>>>>> ERROR watch
>>>>> /home/android_app/jitsi-meet/android/app/build/
intermediates/res/merged/release/values-de
>>>>> ENOSPC
>>>>> {"code":"ENOSPC","errno":"ENOSPC","syscall":"watch
>>>>> /home/android_app/jitsi-meet/android/app/build/
intermediates/res/merged/release/values-de","filename":
"/home/android_app/jitsi-meet/android/app/build/intermediates/res/merged/
release/values-de"}
>>>>> Error: watch
>>>>> /home/android_app/jitsi-meet/android/app/build/
intermediates/res/merged/release/values-de
>>>>> ENOSPC
>>>>> at exports._errnoException (util.js:1018:11)
>>>>> at FSWatcher.start (fs.js:1443:19)
>>>>> at Object.fs.watch (fs.js:1470:11)
>>>>> at NodeWatcher.watchdir
>>>>> (/home/android_app/jitsi-meet/node_modules/sane/src/node_
watcher.js:144:20)
>>>>> at Walker.<anonymous>
>>>>> (/home/android_app/jitsi-meet/node_modules/sane/src/node_
watcher.js:353:12)
>>>>> at emitTwo (events.js:106:13)
>>>>> at Walker.emit (events.js:191:7)
>>>>> at
>>>>> /home/android_app/jitsi-meet/node_modules/walker/lib/walker.js:69:16
>>>>> at go$readdir$cb
>>>>> (/home/android_app/jitsi-meet/node_modules/graceful-fs/
graceful-fs.js:149:14)
>>>>> at FSReqWrap.oncomplete (fs.js:123:15)
>>>>>
>>>>> See http://facebook.github.io/react-native/docs/troubleshooting.html
>>>>> for common problems and solutions.
>>>>>
>>>>>
>>>>> On Thu, Apr 27, 2017 at 8:54 PM, Peter Villeneuve < > petervnv1@gmail.com> > >>>>> wrote:
>>>>>>
>>>>>> Thanks Lyubomir.
>>>>>>
>>>>>> I ended up compiling on my mac and it's working OK now.
>>>>>> Will keep testing.
>>>>>>
>>>>>> Cheers
>>>>>>
>>>>>> On Thu, Apr 27, 2017 at 8:23 PM, Lyubomir Marinov > >>>>>> <lyubomir.marinov@jitsi.org> wrote:
>>>>>>>
>>>>>>> On Thu, Apr 27, 2017 at 2:04 PM, Peter Villeneuve > >>>>>>> <petervnv1@gmail.com> wrote:
>>>>>>> > I tried what you said Lyubomir but it didn't work.
>>>>>>> > It seems to me that after running react-native run-android and
>>>>>>> > pushing the
>>>>>>> > adb onto the phone, there is no packager listening on my machine.
>>>>>>> > Running netstat doesn't show anything listening on that port.
>>>>>>>
>>>>>>> 1. Execute `react-native run-android` which installs the app. If
>>>>>>> react-native packager is not running, the command will start it. It
>>>>>>> it
>>>>>>> doesn't start it, there's probably a problem. You can start it
>>>>>>> yourself with `react-native start`. Leave it open in the
background.
>>>>>>> 2. Start the app and the red screen shows you the error.
>>>>>>> 3. Follow my instructions from my previous mail.
>>>>>>> 4. Shake/click menu again and do Reload.
>>>>>>> 5. The bundle should load from react-native packager.
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> dev mailing list
>>>>>>> dev@jitsi.org
>>>>>>> Unsubscribe instructions and other list options:
>>>>>>> http://lists.jitsi.org/mailman/listinfo/dev
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#19

Hi Peter,

This is now fixed in latest source, you can update and try it.

Regards
damencho

···

On Tue, May 2, 2017 at 10:47 AM, Peter Villeneuve <petervnv1@gmail.com> wrote:

Thanks Damian.
I was ready to pull my hair out :wink:

On Tue, May 2, 2017 at 3:58 PM, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

Yes, this is a known issue which was introduced in a commit yesterday.
There is already a PR fixing this:
https://github.com/jitsi/jitsi-meet/pull/1545. We will most probably
merge it today.

Regards
damencho

On Tue, May 2, 2017 at 7:36 AM, Peter Villeneuve <petervnv1@gmail.com> >> wrote:
> I just tried compiling a release version on both Mint and OSX and both
> failed with these errors:
>
> This warning is caused by a @providesModule declaration with the same
> name
> across two different files.
> Loading dependency graph, done.
> warning: the transform cache was reset.
>
> Unable to resolve module `uid` from
>
> `/home/user/android/jitsi-meet/node_modules/@atlaskit/dropdown-menu/dist/bundle.js`:
> Module does not exist in the module map or in these directories:
>
>
> /home/user/android/jitsi-meet/node_modules/@atlaskit/dropdown-menu/node_modules
> , /home/user/android/jitsi-meet/node_modules
>
> This might be related to
> https://github.com/facebook/react-native/issues/4968
> To resolve try the following:
> 1. Clear watchman watches: `watchman watch-del-all`.
> 2. Delete the `node_modules` folder: `rm -rf node_modules && npm
> install`.
> 3. Reset packager cache: `rm -fr $TMPDIR/react-*` or `npm start
> --reset-cache`.
>
> :app:bundleReleaseJsAndAssets FAILED
>
> FAILURE: Build failed with an exception.
>
> * What went wrong:
> Execution failed for task ':app:bundleReleaseJsAndAssets'.
>> Process 'command 'node'' finished with non-zero exit value 1
>
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output.
>
> BUILD FAILED
>
>
> I did as instructed above (1, 2 and 3) but unfortunately it still
> doesn't
> work.
> It seems I'm not the only one with these RN errors, as can be seen here
> and
> here
>
> has anyone else tried to build a release version of jitsi-meet for
> android?
> Any ideas?
>
>
> Cheers,
> Peter
>
>
>
> On Mon, May 1, 2017 at 2:46 PM, Peter Villeneuve <petervnv1@gmail.com> >> > wrote:
>>
>> I'm now back at my OS X machine and I'm getting the annoying
>> BatchedBridge
>> error
>> again.
>>
>> I think the problem lies with the @providesModule naming collisions
>> referenced above.
>>
>> Is anyone else experiencing these problems? If so, any solutions or
>> workarounds?
>>
>> Cheers,
>> Peter
>>
>> On Sat, Apr 29, 2017 at 8:28 PM, Peter Villeneuve <petervnv1@gmail.com> >> >> wrote:
>>>
>>> I also got these warnings
>>>
>>> npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0
>>> (node_modules/chokidar/node_modules/fsevents):
>>> npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for
>>> fsevents@1.1.1: wanted {"os":"darwin","arch":"any"} (current:
>>> {"os":"linux","arch":"x64"})
>>> npm WARN eslint-plugin-mocha@2.0.0 requires a peer of eslint@^2.0.0
>>> but
>>> none was installed.
>>> npm WARN babel-loader@7.0.0 requires a peer of webpack@2 but none was
>>> installed.
>>>
>>> On Sat, Apr 29, 2017 at 6:55 PM, Peter Villeneuve >> >>> <petervnv1@gmail.com> >> >>> wrote:
>>>>
>>>> Also, I'm running the correct react native version according to the
>>>> settings in package.json
>>>>
>>>> react-native -v
>>>> react-native-cli: 2.0.1
>>>> react-native: 0.42.3
>>>>
>>>>
>>>> On Sat, Apr 29, 2017 at 6:45 PM, Peter Villeneuve >> >>>> <petervnv1@gmail.com> >> >>>> wrote:
>>>>>
>>>>> OK, I went back to try and compile on ubuntu/mint and when I run I
>>>>> get
>>>>> the following errors and the packager doesn't start.
>>>>>
>>>>> I'm running node v6.10.2, npm 4.5.0, JDK 8 on Mint 18.1 Serena
>>>>>
>>>>>
>>>>> │ Running packager on port 8081.
>>>>> │
>>>>> │
>>>>> │
>>>>> │ Keep this packager running while developing on any JS projects.
>>>>> Feel │
>>>>> │ free to close this tab and run your own packager instance if you
>>>>> │
>>>>> │ prefer.
>>>>> │
>>>>> │
>>>>> │
>>>>> │ https://github.com/facebook/react-native
>>>>> │
>>>>> │
>>>>> │
>>>>>
>>>>>
>>>>> └────────────────────────────────────────────────────────────────────────────┘
>>>>> Looking for JS files in
>>>>> /home/android_app/jitsi-meet
>>>>>
>>>>> Loading dependency graph...
>>>>> React packager ready.
>>>>>
>>>>> jest-haste-map: @providesModule naming collision:
>>>>> Duplicate module name: escape-html
>>>>> Paths:
>>>>>
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/node_modules/serve-index/node_modules/escape-html/package.json
>>>>> collides with
>>>>>
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/node_modules/escape-html/package.json
>>>>>
>>>>> This warning is caused by a @providesModule declaration with the
>>>>> same
>>>>> name across two different files.
>>>>> jest-haste-map: @providesModule naming collision:
>>>>> Duplicate module name: debug
>>>>> Paths:
>>>>>
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/node_modules/serve-index/node_modules/debug/package.json
>>>>> collides with
>>>>>
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/node_modules/finalhandler/node_modules/debug/package.json
>>>>>
>>>>> This warning is caused by a @providesModule declaration with the
>>>>> same
>>>>> name across two different files.
>>>>> jest-haste-map: @providesModule naming collision:
>>>>> Duplicate module name: debug
>>>>> Paths:
>>>>>
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/node_modules/connect/node_modules/debug/package.json
>>>>> collides with
>>>>>
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/node_modules/serve-index/node_modules/debug/package.json
>>>>>
>>>>> This warning is caused by a @providesModule declaration with the
>>>>> same
>>>>> name across two different files.
>>>>> jest-haste-map: @providesModule naming collision:
>>>>> Duplicate module name: debug
>>>>> Paths:
>>>>>
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/node_modules/body-parser/node_modules/debug/package.json
>>>>> collides with
>>>>>
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/node_modules/connect/node_modules/debug/package.json
>>>>>
>>>>> This warning is caused by a @providesModule declaration with the
>>>>> same
>>>>> name across two different files.
>>>>> jest-haste-map: @providesModule naming collision:
>>>>> Duplicate module name: escape-html
>>>>> Paths:
>>>>>
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/node_modules/send/node_modules/escape-html/package.json
>>>>> collides with
>>>>>
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/node_modules/serve-index/node_modules/escape-html/package.json
>>>>>
>>>>> This warning is caused by a @providesModule declaration with the
>>>>> same
>>>>> name across two different files.
>>>>> jest-haste-map: @providesModule naming collision:
>>>>> Duplicate module name: debug
>>>>> Paths:
>>>>>
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/node_modules/send/node_modules/debug/package.json
>>>>> collides with
>>>>>
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/node_modules/body-parser/node_modules/debug/package.json
>>>>>
>>>>> This warning is caused by a @providesModule declaration with the
>>>>> same
>>>>> name across two different files.
>>>>> jest-haste-map: @providesModule naming collision:
>>>>> Duplicate module name: bytes
>>>>> Paths:
>>>>>
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/node_modules/raw-body/node_modules/bytes/package.json
>>>>> collides with
>>>>>
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/node_modules/bytes/package.json
>>>>>
>>>>> This warning is caused by a @providesModule declaration with the
>>>>> same
>>>>> name across two different files.
>>>>> jest-haste-map: @providesModule naming collision:
>>>>> Duplicate module name: iconv-lite
>>>>> Paths:
>>>>>
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/node_modules/raw-body/node_modules/iconv-lite/package.json
>>>>> collides with
>>>>>
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/node_modules/iconv-lite/package.json
>>>>>
>>>>> This warning is caused by a @providesModule declaration with the
>>>>> same
>>>>> name across two different files.
>>>>> jest-haste-map: @providesModule naming collision:
>>>>> Duplicate module name: depd
>>>>> Paths:
>>>>>
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/node_modules/depd/package.json
>>>>> collides with
>>>>>
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/node_modules/send/node_modules/depd/package.json
>>>>>
>>>>> This warning is caused by a @providesModule declaration with the
>>>>> same
>>>>> name across two different files.
>>>>> jest-haste-map: @providesModule naming collision:
>>>>> Duplicate module name: mime-types
>>>>> Paths:
>>>>>
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/node_modules/mime-types/package.json
>>>>> collides with
>>>>>
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/node_modules/type-is/node_modules/mime-types/package.json
>>>>>
>>>>> This warning is caused by a @providesModule declaration with the
>>>>> same
>>>>> name across two different files.
>>>>> jest-haste-map: @providesModule naming collision:
>>>>> Duplicate module name: escape-html
>>>>> Paths:
>>>>>
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/node_modules/serve-static/node_modules/escape-html/package.json
>>>>> collides with
>>>>>
>>>>> /home/android_app/jitsi-meet/node_modules/react-native/node_modules/send/node_modules/escape-html/package.json
>>>>>
>>>>> This warning is caused by a @providesModule declaration with the
>>>>> same
>>>>> name across two different files.
>>>>> ERROR watch
>>>>>
>>>>> /home/android_app/jitsi-meet/android/app/build/intermediates/res/merged/release/values-de
>>>>> ENOSPC
>>>>> {"code":"ENOSPC","errno":"ENOSPC","syscall":"watch
>>>>>
>>>>> /home/android_app/jitsi-meet/android/app/build/intermediates/res/merged/release/values-de","filename":"/home/android_app/jitsi-meet/android/app/build/intermediates/res/merged/release/values-de"}
>>>>> Error: watch
>>>>>
>>>>> /home/android_app/jitsi-meet/android/app/build/intermediates/res/merged/release/values-de
>>>>> ENOSPC
>>>>> at exports._errnoException (util.js:1018:11)
>>>>> at FSWatcher.start (fs.js:1443:19)
>>>>> at Object.fs.watch (fs.js:1470:11)
>>>>> at NodeWatcher.watchdir
>>>>>
>>>>> (/home/android_app/jitsi-meet/node_modules/sane/src/node_watcher.js:144:20)
>>>>> at Walker.<anonymous>
>>>>>
>>>>> (/home/android_app/jitsi-meet/node_modules/sane/src/node_watcher.js:353:12)
>>>>> at emitTwo (events.js:106:13)
>>>>> at Walker.emit (events.js:191:7)
>>>>> at
>>>>> /home/android_app/jitsi-meet/node_modules/walker/lib/walker.js:69:16
>>>>> at go$readdir$cb
>>>>>
>>>>> (/home/android_app/jitsi-meet/node_modules/graceful-fs/graceful-fs.js:149:14)
>>>>> at FSReqWrap.oncomplete (fs.js:123:15)
>>>>>
>>>>> See http://facebook.github.io/react-native/docs/troubleshooting.html
>>>>> for common problems and solutions.
>>>>>
>>>>>
>>>>> On Thu, Apr 27, 2017 at 8:54 PM, Peter Villeneuve >> >>>>> <petervnv1@gmail.com> >> >>>>> wrote:
>>>>>>
>>>>>> Thanks Lyubomir.
>>>>>>
>>>>>> I ended up compiling on my mac and it's working OK now.
>>>>>> Will keep testing.
>>>>>>
>>>>>> Cheers
>>>>>>
>>>>>> On Thu, Apr 27, 2017 at 8:23 PM, Lyubomir Marinov >> >>>>>> <lyubomir.marinov@jitsi.org> wrote:
>>>>>>>
>>>>>>> On Thu, Apr 27, 2017 at 2:04 PM, Peter Villeneuve >> >>>>>>> <petervnv1@gmail.com> wrote:
>>>>>>> > I tried what you said Lyubomir but it didn't work.
>>>>>>> > It seems to me that after running react-native run-android and
>>>>>>> > pushing the
>>>>>>> > adb onto the phone, there is no packager listening on my
>>>>>>> > machine.
>>>>>>> > Running netstat doesn't show anything listening on that port.
>>>>>>>
>>>>>>> 1. Execute `react-native run-android` which installs the app. If
>>>>>>> react-native packager is not running, the command will start it.
>>>>>>> It
>>>>>>> it
>>>>>>> doesn't start it, there's probably a problem. You can start it
>>>>>>> yourself with `react-native start`. Leave it open in the
>>>>>>> background.
>>>>>>> 2. Start the app and the red screen shows you the error.
>>>>>>> 3. Follow my instructions from my previous mail.
>>>>>>> 4. Shake/click menu again and do Reload.
>>>>>>> 5. The bundle should load from react-native packager.
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> dev mailing list
>>>>>>> dev@jitsi.org
>>>>>>> Unsubscribe instructions and other list options:
>>>>>>> http://lists.jitsi.org/mailman/listinfo/dev
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#20

I can confirm it's now working. Thanks!

But on Android I'm only able to compile the debug version. How do I compile
an android release version with a different package name and signed by our
keystore?

I've tried changing the package name in the manifest but then that creates
other problems when compiling.

Can you tell me where I need to change the package name without breaking
compilation?

Cheers

···

On Tue, May 2, 2017 at 6:57 PM, Damian Minkov <damencho@jitsi.org> wrote:

Hi Peter,

This is now fixed in latest source, you can update and try it.

Regards
damencho

On Tue, May 2, 2017 at 10:47 AM, Peter Villeneuve <petervnv1@gmail.com> > wrote:
> Thanks Damian.
> I was ready to pull my hair out :wink:
>
> On Tue, May 2, 2017 at 3:58 PM, Damian Minkov <damencho@jitsi.org> > wrote:
>>
>> Hi,
>>
>> Yes, this is a known issue which was introduced in a commit yesterday.
>> There is already a PR fixing this:
>> https://github.com/jitsi/jitsi-meet/pull/1545. We will most probably
>> merge it today.
>>
>> Regards
>> damencho
>>
>>
>> On Tue, May 2, 2017 at 7:36 AM, Peter Villeneuve <petervnv1@gmail.com> > >> wrote:
>> > I just tried compiling a release version on both Mint and OSX and both
>> > failed with these errors:
>> >
>> > This warning is caused by a @providesModule declaration with the same
>> > name
>> > across two different files.
>> > Loading dependency graph, done.
>> > warning: the transform cache was reset.
>> >
>> > Unable to resolve module `uid` from
>> >
>> > `/home/user/android/jitsi-meet/node_modules/@atlaskit/
dropdown-menu/dist/bundle.js`:
>> > Module does not exist in the module map or in these directories:
>> >
>> >
>> > /home/user/android/jitsi-meet/node_modules/@atlaskit/
dropdown-menu/node_modules
>> > , /home/user/android/jitsi-meet/node_modules
>> >
>> > This might be related to
>> > https://github.com/facebook/react-native/issues/4968
>> > To resolve try the following:
>> > 1. Clear watchman watches: `watchman watch-del-all`.
>> > 2. Delete the `node_modules` folder: `rm -rf node_modules && npm
>> > install`.
>> > 3. Reset packager cache: `rm -fr $TMPDIR/react-*` or `npm start
>> > --reset-cache`.
>> >
>> > :app:bundleReleaseJsAndAssets FAILED
>> >
>> > FAILURE: Build failed with an exception.
>> >
>> > * What went wrong:
>> > Execution failed for task ':app:bundleReleaseJsAndAssets'.
>> >> Process 'command 'node'' finished with non-zero exit value 1
>> >
>> > * Try:
>> > Run with --stacktrace option to get the stack trace. Run with --info
or
>> > --debug option to get more log output.
>> >
>> > BUILD FAILED
>> >
>> >
>> > I did as instructed above (1, 2 and 3) but unfortunately it still
>> > doesn't
>> > work.
>> > It seems I'm not the only one with these RN errors, as can be seen
here
>> > and
>> > here
>> >
>> > has anyone else tried to build a release version of jitsi-meet for
>> > android?
>> > Any ideas?
>> >
>> >
>> > Cheers,
>> > Peter
>> >
>> >
>> >
>> > On Mon, May 1, 2017 at 2:46 PM, Peter Villeneuve <petervnv1@gmail.com > > > >> > wrote:
>> >>
>> >> I'm now back at my OS X machine and I'm getting the annoying
>> >> BatchedBridge
>> >> error
>> >> again.
>> >>
>> >> I think the problem lies with the @providesModule naming collisions
>> >> referenced above.
>> >>
>> >> Is anyone else experiencing these problems? If so, any solutions or
>> >> workarounds?
>> >>
>> >> Cheers,
>> >> Peter
>> >>
>> >> On Sat, Apr 29, 2017 at 8:28 PM, Peter Villeneuve < > petervnv1@gmail.com> > >> >> wrote:
>> >>>
>> >>> I also got these warnings
>> >>>
>> >>> npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0
>> >>> (node_modules/chokidar/node_modules/fsevents):
>> >>> npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform
for
>> >>> fsevents@1.1.1: wanted {"os":"darwin","arch":"any"} (current:
>> >>> {"os":"linux","arch":"x64"})
>> >>> npm WARN eslint-plugin-mocha@2.0.0 requires a peer of eslint@^2.0.0
>> >>> but
>> >>> none was installed.
>> >>> npm WARN babel-loader@7.0.0 requires a peer of webpack@2 but none
was
>> >>> installed.
>> >>>
>> >>> On Sat, Apr 29, 2017 at 6:55 PM, Peter Villeneuve > >> >>> <petervnv1@gmail.com> > >> >>> wrote:
>> >>>>
>> >>>> Also, I'm running the correct react native version according to the
>> >>>> settings in package.json
>> >>>>
>> >>>> react-native -v
>> >>>> react-native-cli: 2.0.1
>> >>>> react-native: 0.42.3
>> >>>>
>> >>>>
>> >>>> On Sat, Apr 29, 2017 at 6:45 PM, Peter Villeneuve > >> >>>> <petervnv1@gmail.com> > >> >>>> wrote:
>> >>>>>
>> >>>>> OK, I went back to try and compile on ubuntu/mint and when I run I
>> >>>>> get
>> >>>>> the following errors and the packager doesn't start.
>> >>>>>
>> >>>>> I'm running node v6.10.2, npm 4.5.0, JDK 8 on Mint 18.1 Serena
>> >>>>>
>> >>>>>
>> >>>>> │ Running packager on port 8081.
>> >>>>> │
>> >>>>> │
>> >>>>> │
>> >>>>> │ Keep this packager running while developing on any JS
projects.
>> >>>>> Feel │
>> >>>>> │ free to close this tab and run your own packager instance if
you
>> >>>>> │
>> >>>>> │ prefer.
>> >>>>> │
>> >>>>> │
>> >>>>> │
>> >>>>> │ https://github.com/facebook/react-native
>> >>>>> │
>> >>>>> │
>> >>>>> │
>> >>>>>
>> >>>>>
>> >>>>> └───────────────────────────────────────────────────────────
─────────────────┘
>> >>>>> Looking for JS files in
>> >>>>> /home/android_app/jitsi-meet
>> >>>>>
>> >>>>> Loading dependency graph...
>> >>>>> React packager ready.
>> >>>>>
>> >>>>> jest-haste-map: @providesModule naming collision:
>> >>>>> Duplicate module name: escape-html
>> >>>>> Paths:
>> >>>>>
>> >>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/serve-index/node_modules/escape-html/package.json
>> >>>>> collides with
>> >>>>>
>> >>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/escape-html/package.json
>> >>>>>
>> >>>>> This warning is caused by a @providesModule declaration with the
>> >>>>> same
>> >>>>> name across two different files.
>> >>>>> jest-haste-map: @providesModule naming collision:
>> >>>>> Duplicate module name: debug
>> >>>>> Paths:
>> >>>>>
>> >>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/serve-index/node_modules/debug/package.json
>> >>>>> collides with
>> >>>>>
>> >>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/finalhandler/node_modules/debug/package.json
>> >>>>>
>> >>>>> This warning is caused by a @providesModule declaration with the
>> >>>>> same
>> >>>>> name across two different files.
>> >>>>> jest-haste-map: @providesModule naming collision:
>> >>>>> Duplicate module name: debug
>> >>>>> Paths:
>> >>>>>
>> >>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/connect/node_modules/debug/package.json
>> >>>>> collides with
>> >>>>>
>> >>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/serve-index/node_modules/debug/package.json
>> >>>>>
>> >>>>> This warning is caused by a @providesModule declaration with the
>> >>>>> same
>> >>>>> name across two different files.
>> >>>>> jest-haste-map: @providesModule naming collision:
>> >>>>> Duplicate module name: debug
>> >>>>> Paths:
>> >>>>>
>> >>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/body-parser/node_modules/debug/package.json
>> >>>>> collides with
>> >>>>>
>> >>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/connect/node_modules/debug/package.json
>> >>>>>
>> >>>>> This warning is caused by a @providesModule declaration with the
>> >>>>> same
>> >>>>> name across two different files.
>> >>>>> jest-haste-map: @providesModule naming collision:
>> >>>>> Duplicate module name: escape-html
>> >>>>> Paths:
>> >>>>>
>> >>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/send/node_modules/escape-html/package.json
>> >>>>> collides with
>> >>>>>
>> >>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/serve-index/node_modules/escape-html/package.json
>> >>>>>
>> >>>>> This warning is caused by a @providesModule declaration with the
>> >>>>> same
>> >>>>> name across two different files.
>> >>>>> jest-haste-map: @providesModule naming collision:
>> >>>>> Duplicate module name: debug
>> >>>>> Paths:
>> >>>>>
>> >>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/send/node_modules/debug/package.json
>> >>>>> collides with
>> >>>>>
>> >>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/body-parser/node_modules/debug/package.json
>> >>>>>
>> >>>>> This warning is caused by a @providesModule declaration with the
>> >>>>> same
>> >>>>> name across two different files.
>> >>>>> jest-haste-map: @providesModule naming collision:
>> >>>>> Duplicate module name: bytes
>> >>>>> Paths:
>> >>>>>
>> >>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/raw-body/node_modules/bytes/package.json
>> >>>>> collides with
>> >>>>>
>> >>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/bytes/package.json
>> >>>>>
>> >>>>> This warning is caused by a @providesModule declaration with the
>> >>>>> same
>> >>>>> name across two different files.
>> >>>>> jest-haste-map: @providesModule naming collision:
>> >>>>> Duplicate module name: iconv-lite
>> >>>>> Paths:
>> >>>>>
>> >>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/raw-body/node_modules/iconv-lite/package.json
>> >>>>> collides with
>> >>>>>
>> >>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/iconv-lite/package.json
>> >>>>>
>> >>>>> This warning is caused by a @providesModule declaration with the
>> >>>>> same
>> >>>>> name across two different files.
>> >>>>> jest-haste-map: @providesModule naming collision:
>> >>>>> Duplicate module name: depd
>> >>>>> Paths:
>> >>>>>
>> >>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/depd/package.json
>> >>>>> collides with
>> >>>>>
>> >>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/send/node_modules/depd/package.json
>> >>>>>
>> >>>>> This warning is caused by a @providesModule declaration with the
>> >>>>> same
>> >>>>> name across two different files.
>> >>>>> jest-haste-map: @providesModule naming collision:
>> >>>>> Duplicate module name: mime-types
>> >>>>> Paths:
>> >>>>>
>> >>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/mime-types/package.json
>> >>>>> collides with
>> >>>>>
>> >>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/type-is/node_modules/mime-types/package.json
>> >>>>>
>> >>>>> This warning is caused by a @providesModule declaration with the
>> >>>>> same
>> >>>>> name across two different files.
>> >>>>> jest-haste-map: @providesModule naming collision:
>> >>>>> Duplicate module name: escape-html
>> >>>>> Paths:
>> >>>>>
>> >>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/serve-static/node_modules/escape-html/package.json
>> >>>>> collides with
>> >>>>>
>> >>>>> /home/android_app/jitsi-meet/node_modules/react-native/
node_modules/send/node_modules/escape-html/package.json
>> >>>>>
>> >>>>> This warning is caused by a @providesModule declaration with the
>> >>>>> same
>> >>>>> name across two different files.
>> >>>>> ERROR watch
>> >>>>>
>> >>>>> /home/android_app/jitsi-meet/android/app/build/
intermediates/res/merged/release/values-de
>> >>>>> ENOSPC
>> >>>>> {"code":"ENOSPC","errno":"ENOSPC","syscall":"watch
>> >>>>>
>> >>>>> /home/android_app/jitsi-meet/android/app/build/
intermediates/res/merged/release/values-de","filename":
"/home/android_app/jitsi-meet/android/app/build/intermediates/res/merged/
release/values-de"}
>> >>>>> Error: watch
>> >>>>>
>> >>>>> /home/android_app/jitsi-meet/android/app/build/
intermediates/res/merged/release/values-de
>> >>>>> ENOSPC
>> >>>>> at exports._errnoException (util.js:1018:11)
>> >>>>> at FSWatcher.start (fs.js:1443:19)
>> >>>>> at Object.fs.watch (fs.js:1470:11)
>> >>>>> at NodeWatcher.watchdir
>> >>>>>
>> >>>>> (/home/android_app/jitsi-meet/node_modules/sane/src/node_
watcher.js:144:20)
>> >>>>> at Walker.<anonymous>
>> >>>>>
>> >>>>> (/home/android_app/jitsi-meet/node_modules/sane/src/node_
watcher.js:353:12)
>> >>>>> at emitTwo (events.js:106:13)
>> >>>>> at Walker.emit (events.js:191:7)
>> >>>>> at
>> >>>>> /home/android_app/jitsi-meet/node_modules/walker/lib/
walker.js:69:16
>> >>>>> at go$readdir$cb
>> >>>>>
>> >>>>> (/home/android_app/jitsi-meet/node_modules/graceful-fs/
graceful-fs.js:149:14)
>> >>>>> at FSReqWrap.oncomplete (fs.js:123:15)
>> >>>>>
>> >>>>> See http://facebook.github.io/react-native/docs/
troubleshooting.html
>> >>>>> for common problems and solutions.
>> >>>>>
>> >>>>>
>> >>>>> On Thu, Apr 27, 2017 at 8:54 PM, Peter Villeneuve > >> >>>>> <petervnv1@gmail.com> > >> >>>>> wrote:
>> >>>>>>
>> >>>>>> Thanks Lyubomir.
>> >>>>>>
>> >>>>>> I ended up compiling on my mac and it's working OK now.
>> >>>>>> Will keep testing.
>> >>>>>>
>> >>>>>> Cheers
>> >>>>>>
>> >>>>>> On Thu, Apr 27, 2017 at 8:23 PM, Lyubomir Marinov > >> >>>>>> <lyubomir.marinov@jitsi.org> wrote:
>> >>>>>>>
>> >>>>>>> On Thu, Apr 27, 2017 at 2:04 PM, Peter Villeneuve > >> >>>>>>> <petervnv1@gmail.com> wrote:
>> >>>>>>> > I tried what you said Lyubomir but it didn't work.
>> >>>>>>> > It seems to me that after running react-native run-android and
>> >>>>>>> > pushing the
>> >>>>>>> > adb onto the phone, there is no packager listening on my
>> >>>>>>> > machine.
>> >>>>>>> > Running netstat doesn't show anything listening on that port.
>> >>>>>>>
>> >>>>>>> 1. Execute `react-native run-android` which installs the app. If
>> >>>>>>> react-native packager is not running, the command will start it.
>> >>>>>>> It
>> >>>>>>> it
>> >>>>>>> doesn't start it, there's probably a problem. You can start it
>> >>>>>>> yourself with `react-native start`. Leave it open in the
>> >>>>>>> background.
>> >>>>>>> 2. Start the app and the red screen shows you the error.
>> >>>>>>> 3. Follow my instructions from my previous mail.
>> >>>>>>> 4. Shake/click menu again and do Reload.
>> >>>>>>> 5. The bundle should load from react-native packager.
>> >>>>>>>
>> >>>>>>> _______________________________________________
>> >>>>>>> dev mailing list
>> >>>>>>> dev@jitsi.org
>> >>>>>>> Unsubscribe instructions and other list options:
>> >>>>>>> http://lists.jitsi.org/mailman/listinfo/dev
>> >>>>>>
>> >>>>>>
>> >>>>>
>> >>>>
>> >>>
>> >>
>> >
>> >
>> > _______________________________________________
>> > dev mailing list
>> > dev@jitsi.org
>> > Unsubscribe instructions and other list options:
>> > http://lists.jitsi.org/mailman/listinfo/dev
>>
>> _______________________________________________
>> dev mailing list
>> dev@jitsi.org
>> Unsubscribe instructions and other list options:
>> http://lists.jitsi.org/mailman/listinfo/dev
>
>
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev