Android build not possible

Expo SDK
1

Please provide the following:

  1. SDK Version: 36.0.0
  2. Platforms(Android/iOS/web/all): all

It is a simple example of a web view in Android. The code is as follows:
App.js
import * as React from ‘react’;
import { WebView } from ‘react-native-webview’;

export default class App extends React.Component {
render() {
return <WebView source={{ uri: ‘https://expo.io’ }} style={{ marginTop: 20 }} />;
}
}

And the app.json is
{
“expo”: {
“name”: “attmon”,
“slug”: “attmon”,
“privacy”: “public”,
“sdkVersion”: “36.0.0”,
“platforms”: [
“ios”,
“android”,
“web”
],
“version”: “1.0.0”,
“orientation”: “portrait”,
“icon”: “./assets/icon.png”,
“splash”: {
“image”: “./assets/splash.png”,
“resizeMode”: “contain”,
“backgroundColor”: “#ffffff”
},
“updates”: {
“fallbackToCacheTimeout”: 0
},
“assetBundlePatterns”: [
“**/*”
],
“ios”: {
“supportsTablet”: true
},
“android”: {
“package”: “com.be.attmon”
}
}
}

Error is:
Checking if there is a build in progress…

? Would you like to upload a keystore or have us generate one for you?
If you don’t know what this means, let us handle it! :slight_smile:
false
Unable to find an existing Expo CLI instance for this directory, starting a new one…
Starting Metro Bundler on port 19001.
debug Checking for a newer version of React Native
debug Current version: 0.61.4
debug No release cache found
debug No release cache found
debug Checking for newer releases on GitHub
debug No release cache found
debug Saving W/“6d6386b01438c6ef0acd213d304b5839” to cache
debug No release cache found
debug No release cache found
debug Latest release: 0.60.0
Successfully ran adb reverse. Localhost URLs should work on the connected Android device.
Tunnel ready.
Publishing to channel ‘default’…
Building iOS bundle
Building Android bundle
Building JavaScript bundle [=====================================================================================] 100%Finished building JavaScript bundle in 1213ms.
::ffff:127.0.0.1 - - [09/Jan/2020:20:10:18 +0000] “GET /node_modules/expo/AppEntry.bundle?dev=false&minify=true&hot=false&platform=ios HTTP/1.1” 200 1070605 “-” “axios/0.19.0”
Analyzing assets
Building JavaScript bundle [=====================================================================================] 100%Finished building JavaScript bundle in 1032ms.
::ffff:127.0.0.1 - - [09/Jan/2020:20:10:19 +0000] “GET /node_modules/expo/AppEntry.bundle?dev=false&minify=true&hot=false&platform=android HTTP/1.1” 200 1078303 “-” “axios/0.19.0”
Finished building JavaScript bundle in 1050ms.
::ffff:127.0.0.1 - - [09/Jan/2020:20:10:20 +0000] “GET /node_modules/expo/AppEntry.assets?dev=false&minify=true&hot=false&platform=ios HTTP/1.1” 200 - “-” “axios/0.19.0”
Finished building JavaScript bundle in 2133ms.
::ffff:127.0.0.1 - - [09/Jan/2020:20:10:23 +0000] “GET /node_modules/expo/AppEntry.assets?dev=false&minify=true&hot=false&platform=android HTTP/1.1” 200 - “-” “axios/0.19.0”
Uploading assets
No assets changed, skipped.
Processing asset bundle patterns:

  • C:\Users\mihir\OneDrive\Desktop\attmon***
    Uploading JavaScript bundles
    › Closing Expo server
    (node:12664) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated
    › Stopping Metro bundler
    write ECONNRESET
    Error: write ECONNRESET
    at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:87:16)

I am new to this. Please help.

2

Hi! This can happen due to network issues. Have you tried running this on another network? If you run expo publish, does that finish without error?

3

C:\Users\mihir\OneDrive\Desktop\attmon>expo publish
Unable to find an existing Expo CLI instance for this directory, starting a new one…
Starting Metro Bundler on port 19001.
Tunnel ready.
Publishing to channel ‘default’…
Building iOS bundle
Building Android bundle
Building JavaScript bundle [=====================================================================================] 100%Finished building JavaScript bundle in 2551ms.
Analyzing assets
Building JavaScript bundle [=====================================================================================] 100%Finished building JavaScript bundle in 2149ms.
Finished building JavaScript bundle in 1585ms.
Finished building JavaScript bundle in 1630ms.
Uploading assets
No assets changed, skipped.
Uploading JavaScript bundles
› Closing Expo server
write ECONNRESET
Set EXPO_DEBUG=true in your env to view the stack trace.

The same error is observed.
I have even reinstalled nodejs to see if it works or not twice today.

4

You could try deleting the /.expo/ folder. I have to do that now and then with that error.

Also, if you’re running this from a OneDrive folder, I could see interesting bugs popping up while OneDrive is syncing or whatnot.

5

Tried it and still hasn’t worked. The use of other drives for this purpose yields the same results, so OneDrive doesn’t seem to be the issue.

6

hmmm…i’m already at the end of my expertise :slight_smile:

like @charliecruzan said, maybe check firewall and network type (public/private/domain) in windows? i have ports 19000-19009 open. or try another network?

7

I did try using another ports as well. It seems I’ll have to drop this idea entirely…

8

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