Local builds not working on windows

Build/Submit details page URL
No response
Summary
Expo local builds are not working on windows. Whenever I run eas build --profile preview --platform android --local. I get the following message: Error: Unsupported platform, macOS or Linux is required to build apps for Android.
If eas-cli does not support building Android apps on windows that would be very frustrating because I would like to build on my machine not on your cloud service.
Managed or bare?
Managed
Environment
expo-env-info 1.0.5 environment info:
System:
OS: Windows 10 10.0.22621
Binaries:
Node: 18.13.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.19 - C:\Program Files\nodejs\yarn.CMD
npm: 8.19.3 - C:\Program Files\nodejs\npm.CMD
IDEs:
Android Studio: Version     2<IP_ADDRESS> AI-211.7628.21.2111.8309675
npmPackages:
expo: ~48.0.4 => 48.0.4
react: 18.2.0 => 18.2.0
react-native: 0.71.3 => 0.71.3
Expo Workflow: managed
// -> I have windows 11 btw
┌─────────────────────────────────────────────────────────────────────────┐
│                                                                         │
│   There is a new version of expo-cli available (6.3.2).                 │
│   You are currently using expo-cli 5.4.11                               │
│   Install expo-cli globally using the package manager of your choice;   │
│   for example: npm install -g expo-cli to get the latest version      │
│                                                                         │
└─────────────────────────────────────────────────────────────────────────┘
√ Found all copies of expo-modules-autolinking
All copies of expo-modules-autolinking satisfy ~1.1.0
√ Found all copies of @expo/config-plugins
All copies of @expo/config-plugins satisfy ~6.0.0
√ Found all copies of @expo/prebuild-config
All copies of @expo/prebuild-config satisfy ~6.0.0
🎉 Didn't find any issues with the project!
Error output
Error: Unsupported platform, macOS or Linux is required to build apps for Android.
Reproducible demo or steps to reproduce from a blank project
Idk just run a local android build on Windows.

Message is correct, windows is not supported. You can still use eas build --local on windows inside WSL or run npx expo prebuild and bulid from android studio.
Note that WSL technically it's not officially supported(we do not test it), but it seems to work well.

Ah yes, you can only build for android OS on an Apple OS. Likewise you can only run a build for iOS directly on an android phone. Otherwise you are welcome to line up in the EAS free queue for decades until both platforms are obsolete.

Message is correct, windows is not supported. You can still use eas build --local on windows inside WSL or run npx expo prebuild and bulid from android studio.
Note that WSL technically it's not officially supported(we do not test it), but it seems to work well.

I tried npx expo prebuild and build from android studio, but it gives be development build of app as apk, not the original apps apk. How to fix that?

You will need to sign the apk with a keystore on android studio for it to build a release apk
tutorial for creating a keystore and signing an apk: https://developer.android.com/studio/publish/app-signing#sign-apk

any solution on this guys??

Update to this issue I did get it building on WSL (Ubuntu 22) and can provide instructions if wanted, you cannot use the raw android-sdk, you have to install android studio, make sure the android-sdk is uninstalled and then you can build it. Happy to help if anyone needs help building on WSL. Took me like 3 days to figure all of this out.

Update to this issue I did get it building on WSL (Ubuntu 22) and can provide instructions if wanted, you cannot use the raw android-sdk, you have to install android studio, make sure the android-sdk is uninstalled and then you can build it. Happy to help if anyone needs help building on WSL. Took me like 3 days to figure all of this out.

@OOCAZ i would really appreciate this. I tried it but im getting an error when trying to use any eas command like login or build --local. The error is following:
npm ERR! could not determine executable to run

npm ERR! A complete log of this run can be found in:

Update to this issue I did get it building on WSL (Ubuntu 22) and can provide instructions if wanted, you cannot use the raw android-sdk, you have to install android studio, make sure the android-sdk is uninstalled and then you can build it. Happy to help if anyone needs help building on WSL. Took me like 3 days to figure all of this out.

@OOCAZ i would really appreciate this. I tried it but im getting an error when trying to use any eas command like login or build --local. The error is following:
npm ERR! could not determine executable to run

npm ERR!  Could you give some more verbose errors? The only thing I can think of off the top of my head is, do you have the eas-cli installed globally?
Let me know and we can work through this.

Update to this issue I did get it building on WSL (Ubuntu 22) and can provide instructions if wanted, you cannot use the raw android-sdk, you have to install android studio, make sure the android-sdk is uninstalled and then you can build it. Happy to help if anyone needs help building on WSL. Took me like 3 days to figure all of this out.

@OOCAZ i would really appreciate this. I tried it but im getting an error when trying to use any eas command like login or build --local. The error is following:
npm ERR! could not determine executable to run

npm ERR!  Could you give some more verbose errors? The only thing I can think of off the top of my head is, do you have the eas-cli installed globally?
Let me know and we can work through this.

Hey @OOCAZ, you were right, I figured it out already. Thx. But now I'm facing the next issue. The console is telling me, that it can't locate the Ndk and no SDK provided but I installed openjdk and an SDK.

Update to this issue I did get it building on WSL (Ubuntu 22) and can provide instructions if wanted, you cannot use the raw android-sdk, you have to install android studio, make sure the android-sdk is uninstalled and then you can build it. Happy to help if anyone needs help building on WSL. Took me like 3 days to figure all of this out.

@OOCAZ i would really appreciate this. I tried it but im getting an error when trying to use any eas command like login or build --local. The error is following:
npm ERR! could not determine executable to run

npm ERR!  Could you give some more verbose errors? The only thing I can think of off the top of my head is, do you have the eas-cli installed globally?
Let me know and we can work through this.

Hey @OOCAZ, you were right, I figured it out already. Thx. But now I'm facing the next issue. The console is telling me, that it can't locate the Ndk and no SDK provided but I installed openjdk and an SDK.

So you cannot install the default SDK, you have to uninstall it and then install Android studio for Linux. Once you do that it will walk you through the standard setup and prompt you to install the SDK suite. But if you do not have the old default SDK uninstalled it won't allow you to install the Android Studio SDK.
Ping me again if none of that makes sense.

So you cannot install the default SDK, you have to uninstall it and then install Android studio for Linux. Once you do that it will walk you through the standard setup and prompt you to install the SDK suite. But if you do not have the old default SDK uninstalled it won't allow you to install the Android Studio SDK.
Ping me again if none of that makes sense.

@OOCAZ You know how to install Android Studio on Linux Ubuntu WSL? It's only a command prompted system.

So you cannot install the default SDK, you have to uninstall it and then install Android studio for Linux. Once you do that it will walk you through the standard setup and prompt you to install the SDK suite. But if you do not have the old default SDK uninstalled it won't allow you to install the Android Studio SDK.
Ping me again if none of that makes sense.

@OOCAZ You know how to install Android Studio on Linux Ubuntu WSL? It's only a command prompted system.

Yep. Just download it for Linux, unzip the tar and then navigate inside of it to the studio.sh and execute it. Then it will create a UI for you to finish the install.
I know it's weird, but it's what I did to get it working.

So you cannot install the default SDK, you have to uninstall it and then install Android studio for Linux. Once you do that it will walk you through the standard setup and prompt you to install the SDK suite. But if you do not have the old default SDK uninstalled it won't allow you to install the Android Studio SDK.
Ping me again if none of that makes sense.

@OOCAZ You know how to install Android Studio on Linux Ubuntu WSL? It's only a command prompted system.

Yep. Just download it for Linux, unzip the tar and then navigate inside of it to the studio.sh and execute it. Then it will create a UI for you to finish the install.
I know it's weird, but it's what I did to get it working.

Oh okay, I will try it out tomorrow.  Thanks for your time!

Portanto, você não pode instalar o SDK padrão, é necessário desinstalá-lo e instalar o Android Studio para Linux. Depois de fazer isso, você será guiado pela configuração padrão e solicitará que você instale o pacote SDK. Mas se você não tiver o antigo SDK padrão desinstalado, ele não permitirá a instalação do Android Studio SDK.
Envie-me um ping novamente se nada disso fizer sentido.

@OOCAZVocê sabe como instalar o Android Studio no Linux Ubuntu WSL? É apenas um sistema solicitado por comando.

Sim. Basta baixá-lo para Linux, descompactar o tar e navegar dentro dele até studio.sh e executá-lo. Em seguida, ele criará uma UI para você finalizar a instalação.
Eu sei que é estranho, mas foi o que fiz para que funcionasse.

Eu tenho o mesmo problema, não faz sentido o WSL ter interface grafica, risos.
Pode me ajudar como executar minhas builds --local?

Portanto, você não pode instalar o SDK padrão, é necessário desinstalá-lo e instalar o Android Studio para Linux. Depois de fazer isso, você será guiado pela configuração padrão e solicitará que você instale o pacote SDK. Mas se você não tiver o antigo SDK padrão desinstalado, ele não permitirá a instalação do Android Studio SDK.
Envie-me um ping novamente se nada disso fizer sentido.

@OOCAZVocê sabe como instalar o Android Studio no Linux Ubuntu WSL? É apenas um sistema solicitado por comando.

Sim. Basta baixá-lo para Linux, descompactar o tar e navegar dentro dele até studio.sh e executá-lo. Em seguida, ele criará uma UI para você finalizar a instalação.
Eu sei que é estranho, mas foi o que fiz para que funcionasse.

Eu tenho o mesmo problema, não faz sentido o WSL ter interface grafica, risos.
Pode me ajudar como executar minhas builds --local?

Hey! It doesn't make much sense but I got it working in WSL 2 on both windows 10 and 11. I agree it's unorthodox, but it works, if you need help installing android studio specifically or have any specific errors let me know.

I think google playstore can check the device on which you build your application. If I use WSL to build the application, it will affect my store account. If expo only supports ios and linux, it is a big disadvantage for expo. maybe I'll go back to using react native cli :(

How can this not be made more clear in the docs?! That's disastrously bad. This seems to be utterly impossible to learn beforehand. You seem to have to learn it by trail and error. I discovered this limitation just now, and am still unable to find any material mentioning it in the docs:

Local Builds: https://docs.expo.dev/build-reference/local-builds/
Android Build Process: https://docs.expo.dev/build-reference/android-builds/
EAS Build Limitations: https://docs.expo.dev/build-reference/limitations/

You'd imagine at least one of those articles could mention that Windows is not supported by the EAS CLI.

This seriously doesn't work on Windows??? Are you serious now?
$ eas build --local
√ Select platform » Android
Unsupported platform, macOS or Linux is required to build apps for Android
    Error: build command failed.

Why this is closed? Does anybody could explain the WSL method?

Why this is closed? Does anybody could explain the WSL method?

I haven't found how to do this yet either.

@ananduremanan I can explain it, but essentially you just install the linux version of android studio on wsl and it will work. I can give more in depth set of steps if you want. @suprunchuk same for you too.

@ananduremanan I can explain it, but essentially you just install the linux version of android studio on wsl and it will work. I can give more in depth set of steps if you want. @suprunchuk same for you too.

Hello there 👋, I have been facing hard time figuring out how to build expo preview or development build offline.
So I discovered EAS with --local flag don't support windows, and installed ubuntu on WSL ( I am high schooler and linux OS is something new to me). So this is how it went :
*** long ( and painful) story ahead, if you are short on time, you may skip and go to END***
------------------------------Start------------------------------------------------------
Figuring out how ubuntu works, and accessing my project files on windows in wsl.
Ran eas build in it hoping it works but oh well.... it said Java is not installed.
Installed Java
ran eas build --local
It started downloading gradle-8.0.1-all.zip ( I thought it would use gradle i am using for windows, by this time i realized ubuntu wont take environment variables from windows )
Stopped download, installed gradle and did path setting. ( limited internet, so i wanted to get it worked with gradle's zip i had locally on windows )
Ran eas build
IT STARTED DOWNLOADING GRADLE AGAIN !
I stopped it, than found out, I have to change distributionURL in gradle-wrapper.properties to locally installed zip.
changed it and ran eas and wow it really worked, ( for 10 sec and than....)
I got error about android sdk dont have linux.something ( I set the ANDROID_HOME in ubuntu the same i used in windows ), realizing I have to download diffrent for linux, i did and did parth setting again.
ran eas build, and got error that android license not verified/not found ( something like that )
than I searching on web came on this page and found out as u said above: you need to install Android Studio ( Whole  IDE ) in wsl.
----------------------------END-----------------------------------------------------------------
Also a few days ago,  with many errors and somehow managing Java, Gradle, Kotlin versions to match each other, I somehow built a development build with Android Studio in Windows ( using npx expo start:android) . But the build process kinda took long, like 40 min, and on EAS server it takes like 15 min.
So my questions :
If I can make builds in Android Studio on windows, should still go for eas, ( if it takes lesser time for building or any other benefits, than i would like to use eas ) ?
Also is there any difference between build made from npx expo start:android and eas build  ? thing is I tried to install the build made from android studio over the eas build ( the one from eas server ), noramlly it would simply update the app, but when I tried to install the one from android studio, it said : "App not installed because package conflicts with existing package", so i uninstalled existing app and and than installed the android studio build and it worked fine, got similar error when trying to install previous eas build over android studio build. maybe the credentials are different ?

I think google playstore can check the device on which you build your application. If I use WSL to build the application, it will affect my store account. If expo only supports ios and linux, it is a big disadvantage for expo. maybe I'll go back to using react native cli :(

I guess you can build it in Android Studio too with npx expo start:android
from expo website:

ALSOO : npx expo start:android  will make debug build ( development build ) of your app
to make a release build do this :

You can check out on official website about local-app-development
Alsoo it can be a lil annoying to build it this way, ( i had hard time setting up correct java, kotlin and gradle versions ), idk what problems ios developers might face, eas does everything by itself, so it does feel a lil easy, still if building a android version on windows if what u want, Android Studio got your back !
Hope it helps !

@OOCAZ , somehow I figured it out and as @crystalarcus said it takes a lot of time to build while in linux it takes only few minutes...

I'd start using Flutter at this point, its quite straight forward and well maintained, and a bit faster in performance due to it's 'Ahead-of-Time" (AOT) compilation. ( Also I like Material You Design )

@crystalarcus , Good choice, but flutter job market is so dull, idk why... Also, get linux,  life will be amazing...

@crystalarcus , Good choice, but flutter job market is so dull, idk why... Also, get linux, life will be amazing...

Oh btw, you said you figured it out, how to use EAS in wsl, did you do it using only android-sdk tools or did you downloaded whole android studio ?
also if we have to download the android studio, did you ran eas build --local inside android studio terminal or does it works in direct ubuntu terminal too ?

@crystalarcus , Good choice, but flutter job market is so dull, idk why... Also, get linux, life will be amazing...

Oh btw, you said you figured it out, how to use EAS in wsl, did you do it using only android-sdk tools or did you downloaded whole android studio ? also if we have to download the android studio, did you ran eas build --local inside android studio terminal or does it works in direct ubuntu terminal too ?

I did it using the SDK tools without installing the Android studio on wsl, but the build got failed !!

@crystalarcus , Good choice, but flutter job market is so dull, idk why... Also, get linux, life will be amazing...

Oh btw, you said you figured it out, how to use EAS in wsl, did you do it using only android-sdk tools or did you downloaded whole android studio ? also if we have to download the android studio, did you ran eas build --local inside android studio terminal or does it works in direct ubuntu terminal too ?

I did it using the SDK tools without installing the Android studio on wsl, but the build got failed !!

@ananduremanan so....u tried with Android Studio ? did it work ?

@crystalarcus , Good choice, but flutter job market is so dull, idk why... Also, get linux, life will be amazing...

Oh btw, you said you figured it out, how to use EAS in wsl, did you do it using only android-sdk tools or did you downloaded whole android studio ? also if we have to download the android studio, did you ran eas build --local inside android studio terminal or does it works in direct ubuntu terminal too ?

I did it using the SDK tools without installing the Android studio on wsl, but the build got failed !!

@ananduremanan so....u tried with Android Studio ? did it work ? cuz I am about to download it for linux

Yeah I only ever got it working with Android Studio, the SDK tools never worked for me, but Android studio was working last I checked.

@crystalarcus , Good choice, but flutter job market is so dull, idk why... Also, get linux, life will be amazing...

Oh btw, you said you figured it out, how to use EAS in wsl, did you do it using only android-sdk tools or did you downloaded whole android studio ? also if we have to download the android studio, did you ran eas build --local inside android studio terminal or does it works in direct ubuntu terminal too ?

I did it using the SDK tools without installing the Android studio on wsl, but the build got failed !!

@ananduremanan so....u tried with Android Studio ? did it work ? cuz I am about to download it for linux

Yeah I only ever got it working with Android Studio, the SDK tools never worked for me, but Android studio was working last I checked.

@OOCAZ I need help with this :
I installed Android Studio in Ubuntu, ran eas build -p android --profile development and things went well for 10 min, it was Gradle was running and than suddenly build failed with this :
The message received from the daemon indicates that the daemon has disappeared.
there was some output here -----
`----- End of the daemon log -----
FAILURE: Build failed with an exception.

What went wrong:
Gradle build daemon disappeared unexpectedly (it may have been killed or may have crashed)`

from stackoverflow I found this solution, the answers said Deleting the daemon subfolder in /home/{username}/.gradle will fix the issue, but it didn't. Any suggestion ? ( I tried running it 5 to 6 times, even after restarting laptop, but same error ).

@crystalarcus , Good choice, but flutter job market is so dull, idk why... Also, get linux, life will be amazing...

Oh btw, you said you figured it out, how to use EAS in wsl, did you do it using only android-sdk tools or did you downloaded whole android studio ? also if we have to download the android studio, did you ran eas build --local inside android studio terminal or does it works in direct ubuntu terminal too ?

I did it using the SDK tools without installing the Android studio on wsl, but the build got failed !!

@ananduremanan so....u tried with Android Studio ? did it work ? cuz I am about to download it for linux

Yeah I only ever got it working with Android Studio, the SDK tools never worked for me, but Android studio was working last I checked.

@OOCAZ I need help with this :
I installed Android Studio in Ubuntu, ran eas build -p android --profile development and things went well for 10 min, it was Gradle was running and than suddenly build failed with this :
The message received from the daemon indicates that the daemon has disappeared.
there was some output here -----
----- End of the daemon log -----

FAILURE: Build failed with an exception.

* What went wrong:
Gradle build daemon disappeared unexpectedly (it may have been killed or may have crashed)

from stackoverflow I found this solution, the answers said Deleting the daemon subfolder in /home/{username}/.gradle will fix the issue, but it didn't. Any suggestion ? ( I tried running it 5 to 6 times, even after restarting laptop, but same error ).

So I ran your command and it worked on the eas build systems. But I added the --local tag and it ran and built just fine for me. Are you still having the issue? Any chance you could try not doing a development build and just doing a default or production build? Let me know if that works.

@OOCAZ I ran it for preview build as :
eas build -p android --profile preview
but it get stuck at
starting Daemon
while running gradlew
here is complete log :
Loaded "env" configuration for the "preview" profile: no environment variables specified. Learn more: https://docs.expo.dev/build-reference/variables/
Specified value for "android.package" in app.json is ignored because an android directory was detected in the project.
EAS Build will use the value found in the native code.
✔ Using remote Android credentials (Expo server)
✔ Using Keystore from configuration: Build Credentials dOawfrwgrI (default)
✔ Compressed project files 16s (164 MB)
ANDROID_NDK_HOME environment variable was not specified, continuing build without NDK
[SETUP_WORKINGDIR] Preparing workingdir /tmp/crystalarcus/eas-build-local-nodejs/849b6556-08d0-4b10-8a27-a7b7637bab6c
[START_BUILD] Starting build
  "job": {
    "type": "generic",
    "platform": "android",
    "projectRootDirectory": ".",
    "projectArchive": {
      "type": "PATH",
      "path": "/tmp/crystalarcus/eas-cli-nodejs/89ab9a40-9b4f-46da-8136-e4145a2bc2aa.tar.gz"
    },
    "builderEnvironment": {},
    "cache": {
      "disabled": false,
      "paths": [],
      "clear": false
    },
    "updates": {},
    "buildType": "apk",
    "username": "crystalarcus",
    "experimental": {},
    "mode": "build",
    "triggeredBy": "EAS_CLI"
  }
[READ_PACKAGE_JSON] Using package.json:
[READ_PACKAGE_JSON] {
  "name": "mynotes",
  "version": "1.4.1",
  "scripts": {
    "start": "expo start --dev-client",
    "android": "expo run:android",
    "ios": "expo run:ios",
    "web": "expo start --web",
    "windows": "react-native run-windows"
  },
  "dependencies": {
    "@babel/plugin-proposal-export-namespace-from": "^7.18.9",
    "@expo/config-plugins": "~7.2.2",
    "@expo/webpack-config": "^19.0.0",
    "@miblanchard/react-native-slider": "^2.3.1",
    "@pchmn/expo-material3-theme": "^1.3.1",
    "@react-native-assets/slider": "^7.0.5",
    "@react-native-async-storage/async-storage": "1.18.2",
    "@react-native-community/cli-doctor": "^13.2.0",
    "@react-navigation/drawer": "^6.6.6",
    "@react-navigation/material-top-tabs": "^6.6.5",
    "@react-navigation/native": "^6.1.9",
    "@react-navigation/native-stack": "^6.9.17",
    "@react-navigation/stack": "^6.3.20",
    "babel-plugin-transform-remove-console": "^6.9.4",
    "expo": "^49.0.21",
    "expo-asset": "~8.10.1",
    "expo-clipboard": "~4.3.1",
    "expo-dev-client": "~2.4.12",
    "expo-dynamic-app-icon": "^1.2.0",
    "expo-file-system": "~15.4.5",
    "expo-font": "~11.4.0",
    "expo-print": "~12.4.2",
    "expo-sharing": "~11.5.0",
    "expo-splash-screen": "~0.20.5",
    "expo-status-bar": "~1.6.0",
    "lodash": "^4.17.21",
    "react": "18.2.0",
    "react-dom": "18.2.0",
    "react-native": "0.72.6",
    "react-native-gesture-handler": "~2.12.0",
    "react-native-pager-view": "6.2.0",
    "react-native-paper": "^5.11.1",
    "react-native-paper-dates": "^0.20.5",
    "react-native-push-notification": "^8.1.1",
    "react-native-reanimated": "~3.3.0",
    "react-native-safe-area-context": "4.6.3",
    "react-native-screens": "~3.22.0",
    "react-native-share": "^10.0.2",
    "react-native-slider": "^0.11.0",
    "react-native-tab-view": "^3.5.2",
    "react-native-vector-icons": "^10.0.3",
    "react-native-web": "~0.19.6",
    "react-native-windows": "0.72.21"
  },
  "devDependencies": {
    "@babel/core": "^7.20.0",
    "metro-config": "^0.76.8",
    "sharp-cli": "^4.2.0"
  },
  "private": true
}
[INSTALL_DEPENDENCIES] Running "yarn install" in /tmp/crystalarcus/eas-build-local-nodejs/849b6556-08d0-4b10-8a27-a7b7637bab6c/build directory
[INSTALL_DEPENDENCIES] yarn install v1.22.21
[INSTALL_DEPENDENCIES] [1/4] Resolving packages...
[INSTALL_DEPENDENCIES] [2/4] Fetching packages...
[INSTALL_DEPENDENCIES] [3/4] Linking dependencies...
[INSTALL_DEPENDENCIES] warning "expo-splash-screen ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INSTALL_DEPENDENCIES] warning "react-native ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INSTALL_DEPENDENCIES] warning "react-native > @react-native/codegen ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INSTALL_DEPENDENCIES] warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INSTALL_DEPENDENCIES] warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INSTALL_DEPENDENCIES] warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INSTALL_DEPENDENCIES] warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INSTALL_DEPENDENCIES] warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INSTALL_DEPENDENCIES] warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INSTALL_DEPENDENCIES] [4/4] Building fresh packages...
[INSTALL_DEPENDENCIES] Done in 25.16s.
The NODE_ENV environment variable is required but was not specified. Ensure the project is bundled with Expo CLI or NODE_ENV is set.
Proceeding without mode-specific .env
[READ_APP_CONFIG] Using app configuration:
[READ_APP_CONFIG] {
  "name": "My Notes",
  "slug": "MyNotes",
  "version": "1.4.1",
  "orientation": "portrait",
  "icon": "./assets/gicon.png",
  "userInterfaceStyle": "automatic",
  "splash": {
    "image": "./assets/gsplash.png",
    "resizeMode": "contain",
    "backgroundColor": "#ffffff"
  },
  "assetBundlePatterns": [
    "**/*"
  ],
  "ios": {
    "supportsTablet": true
  },
  "android": {
    "adaptiveIcon": {
      "foregroundImage": "./assets/gicon.png",
      "backgroundColor": "#ffffff",
      "monochromeImage": "./assets/giconmono.png"
    },
    "package": "com.crystalarcus.MyNotes"
  },
  "web": {
    "favicon": "./assets/favicon.png"
  },
  "extra": {
    "eas": {
      "projectId": "2183d8dc-92a6-47f1-af0a-c40813dd869e"
    }
  },
  "sdkVersion": "49.0.0",
  "platforms": [
    "ios",
    "android",
    "web"
  ]
}
[RUN_EXPO_DOCTOR] Running "expo doctor"
[RUN_EXPO_DOCTOR] Running 10 checks on your project...
[RUN_EXPO_DOCTOR] ✔ Check Expo config for common issues
[RUN_EXPO_DOCTOR] ✔ Check package.json for common issues
[RUN_EXPO_DOCTOR] ✔ Check dependencies for packages that should not be installed directly
[RUN_EXPO_DOCTOR] ✔ Check for common project setup issues
[RUN_EXPO_DOCTOR] ✔ Check npm/ yarn versions
[RUN_EXPO_DOCTOR] ✔ Check Expo config (app.json/ app.config.js) schema
[RUN_EXPO_DOCTOR] ✔ Check that packages match versions required by installed Expo SDK
[RUN_EXPO_DOCTOR] ✔ Check for legacy global CLI installed locally
[RUN_EXPO_DOCTOR] ✔ Check that native modules do not use incompatible support packages
[RUN_EXPO_DOCTOR] ✔ Check that native modules use compatible support package versions for installed Expo SDK
[RUN_EXPO_DOCTOR] Didn't find any issues with the project!
[PREBUILD] Skipped running "expo prebuild" because the "android" directory already exists. Learn more about the build process: https://docs.expo.dev/build-reference/android-builds/
[PREPARE_CREDENTIALS] Writing secrets to the project's directory
[PREPARE_CREDENTIALS] Injecting signing config into build.gradle
[RUN_GRADLEW] Running 'gradlew :app:assembleRelease' in /tmp/crystalarcus/eas-build-local-nodejs/849b6556-08d0-4b10-8a27-a7b7637bab6c/build/android
[RUN_GRADLEW] Downloading file:/tmp/crystalarcus/eas-build-local-nodejs/849b6556-08d0-4b10-8a27-a7b7637bab6c/build/android/gradle/wrapper/gradle-8.0.1-all.zip
[RUN_GRADLEW] 10
[RUN_GRADLEW] %.
[RUN_GRADLEW] 20%
[RUN_GRADLEW] 30
[RUN_GRADLEW] %.
[RUN_GRADLEW] 40%.
[RUN_GRADLEW] 50%.
[RUN_GRADLEW] 60%.
[RUN_GRADLEW] 70%.
[RUN_GRADLEW] 80%.
[RUN_GRADLEW] 90%.
[RUN_GRADLEW] 100%
[RUN_GRADLEW] Starting a Gradle Daemon, 1 stopped Daemon could not be reused, use --status for details

and it was stuck there for 30 min untill I ended with ctrl+c.
did it a few times still same.

@crystalarcus The error appears to be this in particular: ANDROID_NDK_HOME environment variable was not specified, continuing build without NDK It looks like you may have not set the Android Home Variable or completely installed Android Studio, feel free to check around, send some screenshots and we will try to get to the bottom of this.

@OOCAZ hello there, so I tried running today with same command but got following error :
complete  log:
crystalarcus@crystalpc/mnt/c/Files/ReactNative/MyNotes$ eas build -p android --profile preview --local
Found eas-cli in your project dependencies.
It's recommended to use the "cli.version" field in eas.json to enforce the eas-cli version for your project.
Learn more: https://github.com/expo/eas-cli#enforcing-eas-cli-version-for-your-project

Found eas-cli in your project dependencies.
It's recommended to use the "cli.version" field in eas.json to enforce the eas-cli version for your project.
Learn more: https://github.com/expo/eas-cli#enforcing-eas-cli-version-for-your-project

Found eas-cli in your project dependencies.
It's recommended to use the "cli.version" field in eas.json to enforce the eas-cli version for your project.
Learn more: https://github.com/expo/eas-cli#enforcing-eas-cli-version-for-your-project

Loaded "env" configuration for the "preview" profile: no environment variables specified. Learn more: https://docs.expo.dev/build-reference/variables/
Specified value for "android.package" in app.json is ignored because an android directory was detected in the project.
EAS Build will use the value found in the native code.
✔ Using remote Android credentials (Expo server)
✔ Using Keystore from configuration: Build Credentials dOawfrwgrI (default)
✔ Compressed project files 7s (6.2 MB)
[SETUP_WORKINGDIR] Preparing workingdir /tmp/crystalarcus/eas-build-local-nodejs/ca299b0d-5354-437b-94a9-b8f0dee604f4
[START_BUILD] Starting build
  "job": {
    "type": "generic",
    "platform": "android",
    "projectRootDirectory": ".",
    "projectArchive": {
      "type": "PATH",
      "path": "/tmp/crystalarcus/eas-cli-nodejs/04f83084-eb82-49f1-8ce2-89bda4461d48.tar.gz"
    },
    "builderEnvironment": {},
    "cache": {
      "disabled": false,
      "paths": [],
      "clear": false
    },
    "updates": {},
    "buildType": "apk",
    "username": "crystalarcus",
    "experimental": {},
    "mode": "build",
    "triggeredBy": "EAS_CLI"
  }
[READ_PACKAGE_JSON] Using package.json:
[READ_PACKAGE_JSON] {
  "name": "mynotes",
  "version": "1.4.2",
  "scripts": {
    "start": "expo start --dev-client",
    "android": "expo run:android",
    "ios": "expo run:ios",
    "web": "expo start --web",
    "windows": "react-native run-windows"
  },
  "dependencies": {
    "@babel/plugin-proposal-export-namespace-from": "^7.18.9",
    "@expo/config-plugins": "~7.2.2",
    "@expo/webpack-config": "^19.0.0",
    "@miblanchard/react-native-slider": "^2.3.1",
    "@pchmn/expo-material3-theme": "^1.3.1",
    "@react-native-assets/slider": "^7.0.5",
    "@react-native-async-storage/async-storage": "1.18.2",
    "@react-native-community/cli-doctor": "^13.2.0",
    "@react-navigation/drawer": "^6.6.6",
    "@react-navigation/material-top-tabs": "^6.6.5",
    "@react-navigation/native": "^6.1.9",
    "@react-navigation/native-stack": "^6.9.17",
    "@react-navigation/stack": "^6.3.20",
    "babel-plugin-transform-remove-console": "^6.9.4",
    "eas-cli": "^5.9.3",
    "expo": "^49.0.21",
    "expo-asset": "~8.10.1",
    "expo-clipboard": "~4.3.1",
    "expo-dev-client": "~2.4.12",
    "expo-dynamic-app-icon": "^1.2.0",
    "expo-file-system": "~15.4.5",
    "expo-font": "~11.4.0",
    "expo-print": "~12.4.2",
    "expo-sharing": "~11.5.0",
    "expo-splash-screen": "~0.20.5",
    "expo-status-bar": "~1.6.0",
    "lodash": "^4.17.21",
    "react": "18.2.0",
    "react-dom": "18.2.0",
    "react-native": "0.72.6",
    "react-native-gesture-handler": "~2.12.0",
    "react-native-pager-view": "6.2.0",
    "react-native-paper": "^5.11.1",
    "react-native-paper-dates": "^0.20.5",
    "react-native-push-notification": "^8.1.1",
    "react-native-reanimated": "~3.3.0",
    "react-native-safe-area-context": "4.6.3",
    "react-native-screens": "~3.22.0",
    "react-native-share": "^10.0.2",
    "react-native-slider": "^0.11.0",
    "react-native-tab-view": "^3.5.2",
    "react-native-theme-switch-animation": "^0.6.0",
    "react-native-vector-icons": "^10.0.3",
    "react-native-web": "~0.19.6",
    "react-native-windows": "0.72.21"
  },
  "devDependencies": {
    "@babel/core": "^7.20.0",
    "metro-config": "^0.76.8",
    "sharp-cli": "^2.1.0"
  },
  "private": true
}
[INSTALL_DEPENDENCIES] Running "yarn install" in /tmp/crystalarcus/eas-build-local-nodejs/ca299b0d-5354-437b-94a9-b8f0dee604f4/build directory
[INSTALL_DEPENDENCIES] yarn install v1.22.21
[INSTALL_DEPENDENCIES] [1/4] Resolving packages...
[INSTALL_DEPENDENCIES] [2/4] Fetching packages...
[INSTALL_DEPENDENCIES] warning<EMAIL_ADDRESS>The engine "yargs" appears to be invalid.
[INSTALL_DEPENDENCIES] [3/4] Linking dependencies...
[INSTALL_DEPENDENCIES] warning "eas-cli ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INSTALL_DEPENDENCIES] warning "eas-cli > @expo/plugin-help > @oclif/core ><EMAIL_ADDRESS>has unmet peer dependency "@types/node@*".
[INSTALL_DEPENDENCIES] warning "eas-cli > @expo/plugin-help > @oclif/core ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INSTALL_DEPENDENCIES] warning "expo-splash-screen ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INSTALL_DEPENDENCIES] warning "react-native ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INSTALL_DEPENDENCIES] warning "react-native > @react-native/codegen ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INSTALL_DEPENDENCIES] warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INSTALL_DEPENDENCIES] warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INSTALL_DEPENDENCIES] warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INSTALL_DEPENDENCIES] warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INSTALL_DEPENDENCIES] warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INSTALL_DEPENDENCIES] warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INSTALL_DEPENDENCIES] warning Workspaces can only be enabled in private projects.
[INSTALL_DEPENDENCIES] [4/4] Building fresh packages...
[INSTALL_DEPENDENCIES] Done in 71.65s.
The NODE_ENV environment variable is required but was not specified. Ensure the project is bundled with Expo CLI or NODE_ENV is set.
Proceeding without mode-specific .env
[READ_APP_CONFIG] Using app configuration:
[READ_APP_CONFIG] {
  "name": "My Notes",
  "slug": "MyNotes",
  "version": "1.4.2",
  "orientation": "portrait",
  "icon": "./assets/gicon.png",
  "userInterfaceStyle": "automatic",
  "splash": {
    "image": "./assets/gsplash.png",
    "resizeMode": "contain",
    "backgroundColor": "#ffffff"
  },
  "assetBundlePatterns": [
    "**/*"
  ],
  "ios": {
    "supportsTablet": true
  },
  "android": {
    "adaptiveIcon": {
      "foregroundImage": "./assets/gicon.png",
      "backgroundColor": "#ffffff",
      "monochromeImage": "./assets/giconmono.png"
    },
    "package": "com.crystalarcus.MyNotes"
  },
  "web": {
    "favicon": "./assets/favicon.png"
  },
  "extra": {
    "eas": {
      "projectId": "2183d8dc-92a6-47f1-af0a-c40813dd869e"
    }
  },
  "sdkVersion": "49.0.0",
  "platforms": [
    "ios",
    "android",
    "web"
  ]
}
[RUN_EXPO_DOCTOR] Running "expo doctor"
[RUN_EXPO_DOCTOR] Running 10 checks on your project...
[RUN_EXPO_DOCTOR] ✔ Check Expo config for common issues
[RUN_EXPO_DOCTOR] ✔ Check package.json for common issues
[RUN_EXPO_DOCTOR] ✔ Check dependencies for packages that should not be installed directly
[RUN_EXPO_DOCTOR] ✔ Check for common project setup issues
[RUN_EXPO_DOCTOR] ✔ Check npm/ yarn versions
[RUN_EXPO_DOCTOR] ✔ Check Expo config (app.json/ app.config.js) schema
[RUN_EXPO_DOCTOR] ✔ Check that packages match versions required by installed Expo SDK
[RUN_EXPO_DOCTOR] ✔ Check for legacy global CLI installed locally
[RUN_EXPO_DOCTOR] ✔ Check that native modules do not use incompatible support packages
[RUN_EXPO_DOCTOR] ✔ Check that native modules use compatible support package versions for installed Expo SDK
[RUN_EXPO_DOCTOR] Didn't find any issues with the project!
[PREBUILD] Skipped running "expo prebuild" because the "android" directory already exists. Learn more about the build process: https://docs.expo.dev/build-reference/android-builds/
[PREPARE_CREDENTIALS] Writing secrets to the project's directory
[PREPARE_CREDENTIALS] Injecting signing config into build.gradle
[RUN_GRADLEW] Running 'gradlew :app:assembleRelease' in /tmp/crystalarcus/eas-build-local-nodejs/ca299b0d-5354-437b-94a9-b8f0dee604f4/build/android
[RUN_GRADLEW] Starting a Gradle Daemon (subsequent builds will be faster)
[RUN_GRADLEW] > Task :gradle-plugin:pluginDescriptors
[RUN_GRADLEW] > Task :expo-dev-launcher-gradle-plugin:pluginDescriptors
[RUN_GRADLEW] > Task :expo-dev-launcher-gradle-plugin:processResources
[RUN_GRADLEW] > Task :gradle-plugin:processResources
[RUN_GRADLEW] > Task :expo-dev-launcher-gradle-plugin:compileKotlin
[RUN_GRADLEW] > Task :expo-dev-launcher-gradle-plugin:compileJava NO-SOURCE
[RUN_GRADLEW] > Task :expo-dev-launcher-gradle-plugin:classes
[RUN_GRADLEW] > Task :expo-dev-launcher-gradle-plugin:jar
[RUN_GRADLEW] > Task :expo-dev-launcher-gradle-plugin:inspectClassesForKotlinIC
[RUN_GRADLEW] > Task :gradle-plugin:compileKotlin
[RUN_GRADLEW] > Task :gradle-plugin:compileJava
[RUN_GRADLEW] NO-SOURCE
[RUN_GRADLEW] > Task :gradle-plugin:classes
[RUN_GRADLEW] > Task :gradle-plugin:jar
[RUN_GRADLEW] > Task :gradle-plugin:inspectClassesForKotlinIC
[RUN_GRADLEW] > Configure project :app
[RUN_GRADLEW]  ℹ  Applying gradle plugin 'expo-dev-launcher-gradle-plugin'<EMAIL_ADDRESS>[RUN_GRADLEW] > Configure project :expo
[RUN_GRADLEW] Using expo modules
[RUN_GRADLEW] - pchmn-expo-material3-theme (1.3.1)
[RUN_GRADLEW]   - expo-application (5.3.1)
[RUN_GRADLEW]   - expo-clipboard (4.3.1)
[RUN_GRADLEW]   - expo-constants (14.4.2)
[RUN_GRADLEW]   - expo-dev-client (2.4.12)
[RUN_GRADLEW]   - expo-dev-launcher (2.4.14)
[RUN_GRADLEW]   - expo-dev-menu (3.2.2)
[RUN_GRADLEW]   - expo-dynamic-app-icon (1.2.0)
[RUN_GRADLEW] - expo-file-system (15.4.5)
[RUN_GRADLEW]   - expo-font (11.4.0)
[RUN_GRADLEW]   - expo-json-utils (0.7.1)
[RUN_GRADLEW]   - expo-keep-awake (12.3.0)
[RUN_GRADLEW]   - expo-manifests (0.7.2)
[RUN_GRADLEW]   - expo-modules-core (1.5.12)
[RUN_GRADLEW]   - expo-modules-core$android-annotation (1.5.12)
[RUN_GRADLEW]   - expo-modules-core$android-annotation-processor (1.5.12)
[RUN_GRADLEW]   - expo-print (12.4.2)
[RUN_GRADLEW]   - expo-sharing (11.5.0)
[RUN_GRADLEW]   - expo-splash-screen (0.20.5)
[RUN_GRADLEW] > Configure project :react-native-reanimated
[RUN_GRADLEW] No AAR for react-native-reanimated found. Attempting to build from source.
[RUN_GRADLEW] Android gradle plugin: 7.4.2
[RUN_GRADLEW] Gradle: 8.0.1
[RUN_GRADLEW] WARNING:Software Components will not be created automatically for Maven publishing from Android Gradle Plugin 8.0. To opt-in to the future behavior, set the Gradle property android.disableAutomaticComponentCreation=true in the `gradle.properties` file or use the new publishing DSL.
[RUN_GRADLEW] The Kotlin Gradle plugin was loaded multiple times in different subprojects, which is not supported and may break the build.
[RUN_GRADLEW] This might happen in subprojects that apply the Kotlin plugins with the Gradle 'plugins { ... }' DSL if they specify explicit versions, even if the versions are equal.
[RUN_GRADLEW] Please add the Kotlin plugin to the common parent project or the root project, then remove the versions in the subprojects.
[RUN_GRADLEW] If the parent project does not need the plugin, add 'apply false' to the plugin line.
[RUN_GRADLEW] See: https://docs.gradle.org/current/userguide/plugins.html#sec:subprojects_plugins_dsl
[RUN_GRADLEW] The Kotlin plugin was loaded in the following projects: ':expo', ':expo-modules-core', ':react-native-gesture-handler', ':react-native-pager-view', ...
[RUN_GRADLEW] The message received from the daemon indicates that the daemon has disappeared.
[RUN_GRADLEW] Build request sent: Build{id=f49c85ad-c36c-4411-a0ff-8327c41f6b7c, currentDir=/tmp/crystalarcus/eas-build-local-nodejs/ca299b0d-5354-437b-94a9-b8f0dee604f4/build/android}
[RUN_GRADLEW] Attempting to read last messages from the daemon log...
[RUN_GRADLEW] Daemon pid: 2137
[RUN_GRADLEW]   log file: /home/crystalarcus/.gradle/daemon/8.0.1/daemon-2137.out.log
[RUN_GRADLEW] ----- Last  20 lines from daemon log file - daemon-2137.out.log -----
[RUN_GRADLEW]   - expo-keep-awake (12.3.0)
[RUN_GRADLEW]   - expo-manifests (0.7.2)
[RUN_GRADLEW]   - expo-modules-core (1.5.12)
[RUN_GRADLEW]   - expo-modules-core$android-annotation (1.5.12)
[RUN_GRADLEW]   - expo-modules-core$android-annotation-processor (1.5.12)
[RUN_GRADLEW]   - expo-print (12.4.2)
[RUN_GRADLEW]   - expo-sharing (11.5.0)
[RUN_GRADLEW]   - expo-splash-screen (0.20.5)
[RUN_GRADLEW] No AAR for react-native-reanimated found. Attempting to build from source.
[RUN_GRADLEW] Android gradle plugin: 7.4.2
[RUN_GRADLEW] Gradle: 8.0.1
[RUN_GRADLEW] WARNING:Software Components will not be created automatically for Maven publishing from Android Gradle Plugin 8.0. To opt-in to the future behavior, set the Gradle property android.disableAutomaticComponentCreation=true in the `gradle.properties` file or use the new publishing DSL.
[RUN_GRADLEW] The Kotlin Gradle plugin was loaded multiple times in different subprojects, which is not supported and may break the build.
[RUN_GRADLEW] This might happen in subprojects that apply the Kotlin plugins with the Gradle 'plugins { ... }' DSL if they specify explicit versions, even if the versions are equal.
[RUN_GRADLEW] Please add the Kotlin plugin to the common parent project or the root project, then remove the versions in the subprojects.
[RUN_GRADLEW] If the parent project does not need the plugin, add 'apply false' to the plugin line.
[RUN_GRADLEW] See: https://docs.gradle.org/current/userguide/plugins.html#sec:subprojects_plugins_dsl
[RUN_GRADLEW] The Kotlin plugin was loaded in the following projects: ':expo', ':expo-modules-core', ':react-native-gesture-handler', ':react-native-pager-view', ...
[RUN_GRADLEW] ----- End of the daemon log -----
[RUN_GRADLEW] FAILURE: Build failed with an exception.
[RUN_GRADLEW] * What went wrong:
[RUN_GRADLEW] Gradle build daemon disappeared unexpectedly (it may have been killed or may have crashed)
[RUN_GRADLEW] * Try:
[RUN_GRADLEW] > Run with --stacktrace option to get the stack trace.
[RUN_GRADLEW] > Run with --info or --debug option to get more log output.
[RUN_GRADLEW] > Run with --scan to get full insights.
[RUN_GRADLEW] * Get more help at https://help.gradle.org
[RUN_GRADLEW] Error: Gradle build failed with unknown error. See logs for the "Run gradlew" phase for more information.

Build failed
Gradle build failed with unknown error. See logs for the "Run gradlew" phase for more information.
npx exited with non-zero code: 1
    Error: build command failed.
^Cystalarcus@crystalpc:/mnt/c/Files/ReactNative/MyNotes$ ^C
crystalarcus@crystalpc:/mnt/c/Files/ReactNative/MyNotes$ ^C
crystalarcus@crystalpc:/mnt/c/Files/ReactNative/MyNotes$

You guys should use this docker image
https://github.com/hmerritt/android-sdk

@rafi16jan not working here :(

@rafi16jan not working here :(

Try adding this on your package.json and run the script:

My problem is build freezing in random tasks 👎

My problem is build freezing in random tasks 👎

Ok, let's go. I FIGURE OUT A DEFINITELY SOLUTION.

Go to your root java folder in WSL (ex.: /usr/lib/jvm/java-17-openjdk-amd64/bin/)

Note: I recommend use a JDK version 17+

Run this code:

sudo keytool -genkey -v -keystore your-upload-key.keystore -alias your-key-alias -keyalg RSA -keysize 2048 -validity 10000

Fill the formulary (save your password)

Place the your-upload-key.keystore file under the android/app directory in your project folder.

Edit the file ~/.gradle/gradle.properties, and add the following (replace ***** with the correct keystore password, alias and key password):

MYAPP_UPLOAD_STORE_FILE=your-upload-key.keystore
MYAPP_UPLOAD_KEY_ALIAS=your-key-alias
MYAPP_UPLOAD_STORE_PASSWORD=*****
MYAPP_UPLOAD_KEY_PASSWORD=*****

Edit the file android/app/build.gradle in your project folder, and add the signing config,

...
android {
    ...
    defaultConfig { ... }
    signingConfigs {
        release {
            if (project.hasProperty('MYAPP_UPLOAD_STORE_FILE')) {
                storeFile file(MYAPP_UPLOAD_STORE_FILE)
                storePassword MYAPP_UPLOAD_STORE_PASSWORD
                keyAlias MYAPP_UPLOAD_KEY_ALIAS
                keyPassword MYAPP_UPLOAD_KEY_PASSWORD
            }
        }
    }
    buildTypes {
        release {
            ...
            signingConfig signingConfigs.release
        }
    }
}
...

Build application

7.1. To generate an AAB file run the code:
npx react-native build-android --mode=release

7.2. To generate an APK file, go to android folder and run the code:
./gradlew assembleRelease

Possible errors
Build is freezing.

Create a file called .wslconfig at the root of the user - C:\Users\YourUsername\.wslconfig
Paste this code inside

[wsl2]
memory=5GB

Shutdown your WSL.

wsl --shutdown

Relaunch your WSL

That's it!

The docs really should be improved to highlight the fact that you can not do eas build --local from Windows!

The docs really should be improved

@marius-haugan They quite should, but why does it matter, just running command eas build --local will show you in terminal that only Linux or Mac is supported. Plus you get to make 30 builds per month / account, you can just make eas build from another account if you run outta limit.......wait this isn't illegal to say here is it ?

Idk if this helps on this issue but: when you run npx expo run:android --variant release, an APK is generated on your-app-folder/android/app/build/outputs/apk/release/app-release.apk
If you want a release bundle (.aab) instead of .apk, I guess you can try this way using pure react-native commands: https://stackoverflow.com/a/76987065
I haven't tested this yet, as I'm not into production yet.
Still, I don't understand why local builds don't work on Windows... Makes no sense 🤡

I don't mind having to now use WSL. Its not so great, and figuring this out at the final step of setting things up sucks, but it does change my whole development environment and expectations, coming from Expo Go.
I just wish the documentation was more obvious about this requirement. WSL might be accessible on Windows, buts its still a virtual environment and not the easiest for people who use Windows 100% to suddenly change over to.

I still don't understand why you can't make local builds on Windows ? like its most used operating system for desktop.

I still don't understand why you can't make local builds on Windows ? like its most used operating system for desktop.

Most used consumer OS... Linux + Unix toolchain is interchangeable and if you add up unix-like OS into one group, Windows is just a necessary minority... Just take a look at this

Most used consumer OS... Linux + Unix toolchain is interchangeable and if you add up unix-like OS into one group, Windows is just a necessary minority... Just take a look at this

Not sure what you're exactly implying here- but Windows has 46.91% professional use (and likely only that low because of many projects like these that don't support it, so devs are forced to use a different OS). So, it may be a slight minority, but its by far the largest single OS that's used for professional use, with all the others being some flavour of Lunix + Unix.
In any case- the docs should be much more clearer about the lack of support for Windows before people waste their time. And tell them straight away that a WSL or Docker solution is required.
I hope that this project will support Windows in the future though, as many other projects have recently come to the table now as well (Bun etc.). Its an OS used by very many devs.

HEYYY, was just learning about Docker and Containers, and realized you can run Ubuntu in Windows inside a Docker Container.

WSL and Docker might work to get the builds working, but connecting to emulators on Windows for live dev is going to still be a pain. This is always the issue with this fragmented way of development, you're running two environments and then have to try and glue them together and it just causes headaches. This is why I'm sticking with Expo Go for now- this dual way leads to wasted time and configuration nightmares.

Most used consumer OS... Linux + Unix toolchain is interchangeable and if you add up unix-like OS into one group, Windows is just a necessary minority... Just take a look at this

Not sure what you're exactly implying here- but Windows has 46.91% professional use (and likely only that low because of many projects like these that don't support it, so devs are forced to use a different OS). So, it may be a slight minority, but its by far the largest single OS that's used for professional use, with all the others being some flavour of Lunix + Unix.
In any case- the docs should be much more clearer about the lack of support for Windows before people waste their time. And tell them straight away that a WSL or Docker solution is required.
I hope that this project will support Windows in the future though, as many other projects have recently come to the table now as well (Bun etc.). Its an OS used by very many devs.

HEYYY, was just learning about Docker and Containers, and realized you can run Ubuntu in Windows inside a Docker Container.

WSL and Docker might work to get the builds working, but connecting to emulators on Windows for live dev is going to still be a pain. This is always the issue with this fragmented way of development, you're running two environments and then have to try and glue them together and it just causes headaches. This is why I'm sticking with Expo Go for now- this dual way leads to wasted time and configuration nightmares.

Just after the global outage of windows 🤓

I would encourage developers to use Linux, even as a dual boot, it's awesome. Just go with Debian or Fedora for start. You learn a lot too. I use Arch btw

Update to this issue I did get it building on WSL (Ubuntu 22) and can provide instructions if wanted, you cannot use the raw android-sdk, you have to install android studio, make sure the android-sdk is uninstalled and then you can build it. Happy to help if anyone needs help building on WSL. Took me like 3 days to figure all of this out.

doing this on wsl by going to the cdrive of windows through mount and navigating my project gives the same error


Call to cuInit results in UNKNOWN_CUDA_ERROR

Reporting a bug
I don't have a conda in my docker image, so I git clone this repo and did python setup.py install.
Numba reports this error:
Error: CUDA device intialisation problem. Message:Error at driver init:
[-1] Call to cuInit results in UNKNOWN_CUDA_ERROR:
Error class: <class 'numba.cuda.cudadrv.error.CudaSupportError'>
I have CUDA 10.1 installed.
System info:
Time Stamp
2020-02-23 16:29:19.076283
Hardware Information
Machine                                       : x86_64
CPU Name                                      : broadwell
CPU count                                     : 56
CFS restrictions                              : None
CPU Features                                  :
64bit adx aes avx avx2 bmi bmi2 cmov cx16 f16c fma fsgsbase invpcid lzcnt mmx
movbe pclmul popcnt prfchw rdrnd rdseed rtm sahf sse sse2 sse3 sse4.1 sse4.2
ssse3 xsave xsaveopt
OS Information
Platform                                      : Linux-4.4.0-142-generic-x86_64-with-debian-stretch-sid
Release                                       : 4.4.0-142-generic
System Name                                   : Linux
Version                                       : #168-Ubuntu SMP Wed Jan 16 21:00:45 UTC 2019
OS specific info                              : debianstretch/sid
glibc info                                    : glibc 2.3.4
Python Information
Python Compiler                               : GCC 5.4.0 20160609
Python Implementation                         : CPython
Python Version                                : 3.6.8
Python Locale                                 :
LLVM information
LLVM version                                  : 8.0.0
CUDA Information
Error: CUDA device intialisation problem. Message:Error at driver init:
[-1] Call to cuInit results in UNKNOWN_CUDA_ERROR:
Error class: <class 'numba.cuda.cudadrv.error.CudaSupportError'>
ROC Information
ROC available                                 : False
Error initialising ROC due to                 : No ROC toolchains found.
No HSA Agents found, encountered exception when searching:
Error at driver init:
NUMBA_HSA_DRIVER /opt/rocm/lib/libhsa-runtime64.so is not a valid file path.  Note it must be a filepath of the .so/.dll/.dylib or the driver:
SVML Information
SVML state, config.USING_SVML                 : False
SVML library found and loaded                 : False
llvmlite using SVML patched LLVM              : True
SVML operational                              : False
Threading Layer Information
TBB Threading layer available                 : False
+--> Disabled due to                          : Unknown import problem.
OpenMP Threading layer available              : True
+--> Vendor:                                  : GNU
Workqueue Threading layer available           : True
Numba Environment Variable Information
None set.
Conda Information
Conda not present/not working.
Error was [Errno 2] No such file or directory: 'conda': 'conda'

[ -] I am using the latest released version of Numba (most recent is visible in
the change log (https://github.com/numba/numba/blob/master/CHANGE_LOG).
[ ] I have included below a minimal working reproducer (if you are unsure how
to write one see http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports).

Thanks for the report. Do you have CUDA Toolkit installed in the container? CUDA support requires this and a suitable CUDA driver present on the host (and the container to have permissions etc to use it and the hardware).

Closing this issue due to lack of information. If more information becomes available please add it and reopen the issue. Thanks.


Removing Sergei so that we don't pollute him every time

[ci skip] NO_CI

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please update team


HADOOP-17711. Fix divide by zero in LoadBalancingKMSClientProvider.

This pr fixes the issue here.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 36s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
35m 24s

trunk passed

+1 :green_heart:
compile
22m 36s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
19m 51s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
checkstyle
1m  5s

trunk passed

+1 :green_heart:
mvnsite
1m 33s

trunk passed

+1 :green_heart:
javadoc
1m  4s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
1m 39s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
spotbugs
2m 25s

trunk passed

+1 :green_heart:
shadedclient
16m 20s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

-1 :x:
mvninstall
0m 32s
/patch-mvninstall-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

-1 :x:
compile
1m  0s
/patch-compile-root-jdkUbuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04.txt
root in the patch failed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04.

-1 :x:
javac
1m  0s
/patch-compile-root-jdkUbuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04.txt
root in the patch failed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04.

-1 :x:
compile
0m 54s
/patch-compile-root-jdkPrivateBuild-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08.txt
root in the patch failed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08.

-1 :x:
javac
0m 54s
/patch-compile-root-jdkPrivateBuild-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08.txt
root in the patch failed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08.

-1 :x:
blanks
0m  0s
/blanks-eol.txt
The patch has 1 line(s) that end in blanks. Use git apply --whitespace=fix <<patch_file>>. Refer https://git-scm.com/docs/git-apply

-1 :x:
blanks
0m  0s
/blanks-tabs.txt
The patch 1 line(s) with tabs.

-0 :warning:
checkstyle
0m 43s
/results-checkstyle-hadoop-common-project_hadoop-common.txt
hadoop-common-project/hadoop-common: The patch generated 1 new + 5 unchanged - 0 fixed = 6 total (was 5)

-1 :x:
mvnsite
0m 35s
/patch-mvnsite-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

+1 :green_heart:
javadoc
0m 41s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
1m 19s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

-1 :x:
spotbugs
0m 33s
/patch-spotbugs-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

-1 :x:
shadedclient
6m 32s

patch has errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
0m 34s
/patch-unit-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

+1 :green_heart:
asflicense
0m 24s

The patch does not generate ASF License warnings.

111m 38s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3048/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3048

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux e9182ebd0207 4.15.0-136-generic #140-Ubuntu SMP Thu Jan 28 05:20:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / f2fdbbd2600245ccc7bf97a1136e759dd2c3c395

Default Java
Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3048/1/testReport/

Max. process+thread count
541 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3048/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 52s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
33m 11s

trunk passed

+1 :green_heart:
compile
22m 35s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
24m 38s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
checkstyle
1m  7s

trunk passed

+1 :green_heart:
mvnsite
1m 43s

trunk passed

+1 :green_heart:
javadoc
1m  6s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 44s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
2m 44s

trunk passed

+1 :green_heart:
shadedclient
19m  8s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

-1 :x:
mvninstall
0m 31s
/patch-mvninstall-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

-1 :x:
compile
1m  0s
/patch-compile-root-jdkUbuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04.txt
root in the patch failed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04.

-1 :x:
javac
1m  0s
/patch-compile-root-jdkUbuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04.txt
root in the patch failed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04.

-1 :x:
compile
0m 53s
/patch-compile-root-jdkPrivateBuild-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10.txt
root in the patch failed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10.

-1 :x:
javac
0m 53s
/patch-compile-root-jdkPrivateBuild-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10.txt
root in the patch failed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 45s

the patch passed

-1 :x:
mvnsite
0m 36s
/patch-mvnsite-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

+1 :green_heart:
javadoc
0m 43s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 18s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

-1 :x:
spotbugs
0m 34s
/patch-spotbugs-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

-1 :x:
shadedclient
6m 36s

patch has errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
0m 34s
/patch-unit-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

+1 :green_heart:
asflicense
0m 23s

The patch does not generate ASF License warnings.

117m 28s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3048/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3048

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux 8b467e564395 4.15.0-142-generic #146-Ubuntu SMP Tue Apr 13 01:11:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / f554b830dfff38a8f8df99a8ad9d000cf774f002

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3048/2/testReport/

Max. process+thread count
520 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3048/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.


Fix GA feedback custom event

Currently we are not able to record the feedback sent to GA through the form at the bottom of each page.
We probably need to set some custom event in GS. See this.

resolved


Crashes after first SCTE-35 cue recognition

Hi and thanks a lot for such a useful utility!
But I faced a problem running it on my Ubuntu 18.04.1 LTS.
I have a file with several SCTE-35 cues, but the program only recognizes one and then chrashes like this:
~/scte35dump/target/debug$ ./scte35dump file ~/Sft-1.ts
new table for pid 2030, program 2030
unhandled pid 17
[PMT pid:2030 program:2030] new entry PID 2031
[PMT pid:2030 program:2030] new entry PID 2032
[PMT pid:2030 program:2030] new entry PID 2035
Found SCTE-35 data on PID 2035 (0x7f3)
unhandled pid 20
SpliceInfoHeader { protocol_version: 0, encrypted_packet: false, encryption_algorithm: None, pts_adjustment: 0, cw_index: 255, tier: 4095 } SpliceInsert {
    splice_event_id:<PHONE_NUMBER>,
    reserved: 127,
    splice_detail: Insert {
        network_indicator: Out,
        splice_mode: Program(
            Timed(
                Some(
<PHONE_NUMBER>
                )
            )
        ),
        duration: Some(
            SpliceDuration {
                return_mode: Manual,
                duration: 14850000
            }
        ),
        unique_program_id: 1,
        avail_num: 21,
        avails_expected: 255
    }
}
thread 'main' panicked at 'index out of bounds: the len is 3 but the index is 3', /home/lastrixx/.cargo/registry/src/github.com-1ecc6299db9ec823/scte35-reader-0.3.0/src/lib.rs:230:51
note: Run with `RUST_BACKTRACE=1` for a backtrace.

I'd appreciate very much if you could help me with this and I can provide any addinional information you may need.
Here is the backtrace which it gives when env RUST_BACKTRACE=1 is ON:
new table for pid 2030, program 2030
unhandled pid 17
[PMT pid:2030 program:2030] new entry PID 2031
[PMT pid:2030 program:2030] new entry PID 2032
[PMT pid:2030 program:2030] new entry PID 2035
Found SCTE-35 data on PID 2035 (0x7f3)
unhandled pid 20
SpliceInfoHeader { protocol_version: 0, encrypted_packet: false, encryption_algorithm: None, pts_adjustment: 0, cw_index: 255, tier: 4095 } SpliceInsert {
    splice_event_id:<PHONE_NUMBER>,
    reserved: 127,
    splice_detail: Insert {
        network_indicator: Out,
        splice_mode: Program(
            Timed(
                Some(
<PHONE_NUMBER>
                )
            )
        ),
        duration: Some(
            SpliceDuration {
                return_mode: Manual,
                duration: 14850000
            }
        ),
        unique_program_id: 1,
        avail_num: 21,
        avails_expected: 255
    }
}
thread 'main' panicked at 'index out of bounds: the len is 3 but the index is 3', /home/lastrixx/.cargo/registry/src/github.com-1ecc6299db9ec823/scte35-reader-0.3.0/src/lib.rs:230:51
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
             at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
   1: std::sys_common::backtrace::print
             at libstd/sys_common/backtrace.rs:71
             at libstd/sys_common/backtrace.rs:59
   2: std::panicking::default_hook::{{closure}}
             at libstd/panicking.rs:211
   3: std::panicking::default_hook
             at libstd/panicking.rs:227
   4: std::panicking::rust_panic_with_hook
             at libstd/panicking.rs:511
   5: std::panicking::continue_panic_fmt
             at libstd/panicking.rs:426
   6: rust_begin_unwind
             at libstd/panicking.rs:337
   7: core::panicking::panic_fmt
             at libcore/panicking.rs:92
   8: core::panicking::panic_bounds_check
             at libcore/panicking.rs:60
   9: scte35_reader::SpliceDescriptor::parse
             at /home/lastrixx/.cargo/registry/src/github.com-1ecc6299db9ec823/scte35-reader-0.3.0/src/lib.rs:230
  10: <scte35_reader::SpliceDescriptorIter<'buf> as core::iter::iterator::Iterator>::next
             at /home/lastrixx/.cargo/registry/src/github.com-1ecc6299db9ec823/scte35-reader-0.3.0/src/lib.rs:291
  11: <scte35dump::mpegts::DumpSpliceInfoProcessor as scte35_reader::SpliceInfoProcessor>::process
             at src/mpegts.rs:12
  12: <scte35_reader::Scte35SectionProcessor<P, Ctx> as mpeg2ts_reader::psi::SectionProcessor>::start_section
             at /home/lastrixx/.cargo/registry/src/github.com-1ecc6299db9ec823/scte35-reader-0.3.0/src/lib.rs:332
  13: <mpeg2ts_reader::psi::SectionPacketConsumer<P>>::consume
             at /home/lastrixx/.cargo/registry/src/github.com-1ecc6299db9ec823/mpeg2ts-reader-0.4.0/src/psi.rs:443
  14: <scte35dump::mpegts::Scte35StreamConsumer as mpeg2ts_reader::demultiplex::PacketFilter>::consume
             at src/mpegts.rs:60
  15: <mpeg2ts_reader::demultiplex::Demultiplex<Ctx>>::push
             at /home/lastrixx/scte35dump/<packet_filter_switch macros>:8
             at /home/lastrixx/.cargo/registry/src/github.com-1ecc6299db9ec823/mpeg2ts-reader-0.4.0/src/demultiplex.rs:690
  16: scte35dump::file_main
             at src/main.rs:72
  17: scte35dump::main
             at src/main.rs:102
  18: std::rt::lang_start::{{closure}}
             at /checkout/src/libstd/rt.rs:74
  19: std::panicking::try::do_call
             at libstd/rt.rs:59
             at libstd/panicking.rs:310
  20: __rust_maybe_catch_panic
             at libpanic_unwind/lib.rs:105
  21: std::rt::lang_start_internal
             at libstd/panicking.rs:289
             at libstd/panic.rs:392
             at libstd/rt.rs:58
  22: std::rt::lang_start
             at /checkout/src/libstd/rt.rs:74
  23: main
  24: __libc_start_main
  25: _start

FWIW, initial attempt at a fix in https://github.com/dholroyd/scte35-reader/commit/c6be75ceda7c9f6ef214a8679973d1101808fcfb

Hi! I will try to upload the stream fragments somewhere.
Meanwhile, I'm completely new to Rust. Woul you plese explain how should I update that particular sct35-reader library on my machine? 'cargo fetch' doesn't help

A pair of 4GB files is not quite the kind of 'minimal' I had in mind - my poor internet connection is :boom:  :grinning:
Don't worry about updating sct35-reader if you're unfamiliar, I'll push out new releases once I've had the chance to download and test with the examples you've provided, then hopefully you can just cargo install the new version of scte35dump.

Works! This means that I don't need to endlessly scroll&click the DVB Inspector tree any more - hat's pure happines, thank you so much!!!

Glad to hear it works :+1:
By the way, I am curious to understand how others use scte35dump in their workflows.  If you feel like sharing a few words about the problems it solves for you, that's would be awesome!

I'm doing some analytics about commercial breaks, their durations and position in the program.

Hi, Observing similar crash issue,
SpliceInfoHeader { protocol_version: 0, encrypted_packet: false, encryption_algorithm: None, pts_adjustment:<PHONE_NUMBER>, cw_index: 0, tier: 4095 } TimeSignal {
splice_time: Timed(
Some(
1683572058,
),
),
}
thread 'main' panicked at 'assertion failed: (left == right)
left: 144,
right: 152', /home/vagrant/.cargo/registry/src/github.com-1ecc6299db9ec823/scte35-reader-0.6.0/src/lib.rs:536:9
note: Run with RUST_BACKTRACE=1 environment variable to display a backtrace.
Link for sample file for analysis > http://www.mediafire.com/file/35mlgowmq10x16a/time_signal.ts/file

@ashoktk11; opened #4, since your report is a distinct problem from the one originally reported on this ticket.


add new call tracker

Signed-off-by: reiase<EMAIL_ADDRESS>

Codecov Report

Merging #1153 (b948d16) into main (b3f814e) will decrease coverage by 0.06%.
The diff coverage is 75.00%.

:exclamation: Current head b948d16 differs from pull request most recent head 9768891. Consider uploading reports for the commit 9768891 to get more accurate results

@@            Coverage Diff             @@
##             main    #1153      +/-   ##
==========================================
- Coverage   65.90%   65.84%   -0.07%
==========================================
  Files         226      226
  Lines       10336    10341       +5
  Branches     1742     1740       -2
==========================================
- Hits         6812     6809       -3
- Misses       3073     3078       +5
- Partials      451      454       +3

Impacted Files
Coverage Δ

towhee/functional/__init__.py
66.66% <62.50%> (-12.50%)
:arrow_down:

towhee/functional/mixins/entity_mixin.py
94.04% <84.21%> (ø)

towhee/hparam/hyperparameter.py
70.38% <87.50%> (+1.44%)
:arrow_up:

towhee/hparam/__init__.py
100.00% <100.00%> (ø)

towhee/dataframe/dataframe.py
73.10% <0.00%> (-1.05%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b3f814e...9768891. Read the comment docs.

/lgtm


Selyse Baratheon v. Nymeria Sand - cannot obtain back intrigue icon

bug i just noticed in a game:

Nymeria is used to remove a INT icon from Selyse
Selyse action is used to give her a INT icon back
the latter doesn't work, and Selyse remains without a INT icon and cannot initiate such a challenge.
Trying to use /give-icon on her didn't work either

and to make things more interesting: Selyse was returned to hand using Ghaston Grey. When, turns later, she was put back into play, she was still without the INT icon, with no way of giving the icon back to her with /give-icon

The implementation was overriding addIcon which meant any attempt to give Selyse an icon - through her ability, through another characters effect, through the chat commands - would fail and instead call the action method. It's also why she didn't gain it back when returned to hand - the unapply for the removeIcon effect calls, Card.addIcon, which would again just trigger her prompt.


how to handle AEP with weird threshold

AEP histogram has just one bin all 1s or 0s

when threshold is really low or really high


Switch inclusion of header files from <> to ""

Would you like to reconsider this proposal?

@elfring Can you elaborate?
To clarify: We currently almost use always use <>, this issue is suggesting using "" for all the headers local within the pelikan repo (i.e. excluding deps – ccommon and systems headers)

Do the include statements which are using angle brackets so far refer to header files that belong to application programming interfaces?

@elfring Yes. We basically were using angle brackets for everything.

Is the use of angle brackets more appropriate occasionally?

@elfring I'm not exactly sure what the best practice is. I've seen people using angle brackets only for system libraries, and I've seen the other extreme where angle brackets are used liberally (twemcache, twemproxy actually fell into the latter camp).
For now, we have restricted angle brackets to be used for anything that's not under pelikan/src, including ccommon includes, which seems to a little more liberal than average. This is mostly to make local includes – such as having the .c include the corresponding .h – as concise as possible.
If anybody knows more feel free to comment.


Complete removal of simple form

@ofsound Ok, this is ready for a little css love on

[ ] login form
[ ] sign up form
[ ] create new password form (after a password reset. You can reset password and look in the rails logs for the link to use to get to it)

One thing we have deal with is feedback when a field doesn't pass validation or is left empty. Do we want to display that inline with a field? Or as a list of "things wrong" at the top of the form? If you style some example I can plug it in, or I can just dump the errors out at the top....

@sudara I think we can close this branch? I updated the CSS for the ex-simple forms. For the failed form validations, I put an orange outline on the missing fields. I think that combined with the the flash message up top might be alright for now.

@ofsound Perfecto — I looked into it and it would be pretty trivial to put errors next to the field, so we can see how it goes....


ci: update arduino triggers

Summary
This PR adjusts the Arduino CI paths for GH Actions.
Checklist

[ ] Documentation (if necessary)
[ ] Tests (if necessary)
[x] Ready to be merged

@faustbrian
gtg 👍
Hopefully this can help kick start the #126 workflow again too.

It would be better to use the GITHUB_WORKSPACE environment variable as documented at https://help.github.com/en/articles/virtual-environments-for-github-actions#environment-variables to avoid having to change that path if they do change it internally.

@faustbrian
Right on, the path only changed bc we switched to Actions which has different dir names, and the bash scripts copy to an Arduino library dir that has to be in home; so that workspace variable isn’t all that helpful in this case.
I can add it if you’d like, but we’d still need to use the system paths for the majority of the workflow.

Should something like mv ${GITHUB_WORKSPACE}/* ~/Arduino/libraries/cpp-client/ work in that case if only the arduino folder has to stay where it is?

@sleepdefic1t https://github.com/ArkEcosystem/cpp-client/runs/238286766 looks good?

@faustbrian
Looks good to me 👍


How to properly use unreadCount, new (lastMessage) and seen (lastMessage)?

Hi all, I am trying to put the unread count for each chat room.
I have exactly two users per chatRoom.
If I set the unreadCount(within the chatroom object) in the database it will show it to all the users including the user who sent the messages.
Since I am getting a list of all the chat rooms initially without the messages in it. I don't have a proper way to show the unread count without calling get messages for all the chat rooms one by one.
If I set the new flag to true in the database it will also highlight the message to both sender and user.
Did I miss something or am I doing something wrong here?
Is there a way to handle this within the package? A way to show the user that he/she has new messages per chat room (at least without the count)

You can either use unreadCount or lastMessage.
It seems like your issue is a limitation in your own code implementation or backend.
Which backend are you using?

I am using aws appsync

No, if you set new, the last message will be displayed as new whatever user is receiving it.
You need to set new logic on your own, check which user you want to show this and implement the conditional param accordingly.

For example, the demo code is:
new: message.sender_id !== this.currentUserId && (!message.seen || !message.seen[this.currentUserId])

Thanks. That makes sense.


Why all of data implements is in AppDataManager?

It's very strange . Is there some better way do this?

Yes, we are thinking on this simplify it. May be we can insert interactors between these.

I do this in kotlin by delegete.
class DataManager(api: ApiDataManager, db: DbManager): ApiInterface by api, DbInterface by db

Just Syntactic sugar, not Solution

We have made the modifications. Please refer to this repository which simplifies it into interactors:
android-mvp-interactor-architecture)


Funds stucked since force closure

TL;DR
I run into a force closure with Mutiny Wallet and funds are stucked since 5 aug 2024.
Background and issue
I decided to close the channel that I had with mutiny a couple of weeks ago.
Went to the menu section for channels and clicked to close it. I was returned an exception that says:

Channel closed because of an exception: Unable to come to consensus about closing feerate, remote wants something (431 sat) lower than our min fee (770 sat)

This is the message that appears in the transaction details of the force closure, along with the Channel ID and the date (5 aug 2024).
Since then, I though that I had to wait and the sats would appear eventually in the onchain wallet section. Indeed, if I go to the overview section where LN, fedimint and OC balances are shown separately, I can see the sats under the OC funds.
I tried to transfer these sats to a new wallet with an OC transaction, but the issue seems to be that there is no actual sats in my OC wallet and any amount I try to transfer is "higher than the wallet balance".

Provide logs and we can try to take a look

Thanks for the support!
Here are the logs I can export from Mutiny app as of today:
mutiny-logs.txt

Having the same exact issue.  Was this ever resolved? What was the fix?

Having the same exact issue.  Was this ever resolved? What was the fix?

No solution yet.

Having the same exact issue. Was this ever resolved? What was the fix?

No fix at the moment, no

Your channel close has not been confirmed yet. You can either wait for it to confirm or accelerate it yourself. And then wait a few days for the sweep transaction once the channel force closure confirms. Nothing else we can do here.
https://mempool.space/tx/1f6fd32780e14fe896e9aca2b3119f3d9d2740d37940bdebb816297c6614fbee


[feature] Implement Bug and Feature Issue Templates

This proposal aims to enhance collaboration by introducing bug and feature issue templates. These templates provide a standardized format for reporting bugs and suggesting new features.
If you have any suggestions on what the content of the template should contain, let me know. thank you!
under gssoc23 assign this to me

can you check this issue? @goodchai0 thank you!


@attr boolean/number setter function called with an empty string (v2-beta)

This is maybe related to #117, but not 100% sure on that.
With a component defined like this:
import { controller, attr } from '@github/catalyst'

@controller
class TestComponentElement extends HTMLElement {

  @attr get booleanProp() {
    return false
  }
  set booleanProp( _v: boolean ) {
    console.dir( `booleanProp type: ${ typeof _v }` )
    console.dir( `booleanProp value: '${ _v }'` )
  }

  connectedCallback() {
    this.booleanProp = true
  }

}

and html like this (note the lack of an initial boolean-prop value):
<test-component></test-component>

I get these log messages:
booleanProp type: boolean
booleanProp value: 'true'
booleanProp type: string
booleanProp value: ''

Changing the html to include an initial value like this:
<test-component boolean-prop='anything'></test-component>

get's rid of that final empty string call:
booleanProp type: boolean
booleanProp value: 'true'

Maybe this is a limitation? Hopefully this isn't another ghost bug, sorry about the last one 🫣

Thanks for the report! This is very helpful, it looks like a bug.
Would you like to submit a PR with a failing test case? That would be very helpful!

Hi Keith, no problem I'll do that soon


Optimize world diff collection

Problem
World diff collection involves:

iterating over all replicated entities and their replicated components to identify which components need to be sent to clients
allocating intermediary 'world diffs' for each client, which contain all the diffs they will be sent this tick

Solution
The first problem can be mitigated with per-entity change detection, so you don't need to iterate over components in entities that haven't changed in a while.
Here are three ideas to mitigate the second problem (as discussed on discord).

Serialize diffs directly into per-client buffers instead of allocating intermediary representations. Easy to implement, fast. Can work with diff fragmentation by allocating a new buffer representing a new packet whenever the current buffer is packed (with some byte shuffling to manage entity boundaries).
Build a world diff history cache that has per-tick diffs for replicated entities (only most recent changes are cached). Client packets are built by directly serializing into buffers from the diff cache. Moderate difficulty to implement, faster than current code but slower than (1) because the cache must be allocated. Also supports diff fragmentation.
Bundle-based replication using auto-generated systems to collect diffs. Hard to implement, equivalent to (1). Also supports diff fragmentation.

In conclusion, (1) seems like a safe bet.

https://github.com/bevyengine/bevy/issues/5097 should also speedup iteration.

Closed by #46.


Routing Problem - Step 5 - Angular 2 Socially

Hello,
i'm having problems when add a ROUTER_PROVIDER and all his friends...
My Code:
import 'reflect-metadata'
import 'zone.js/dist/zone'
import {Component,provide} from '@angular/core'
import {bootstrap} from 'angular2-meteor-auto-bootstrap'
import {ROUTER_PROVIDERS,ROUTER_DIRECTIVES,RouteConfig} from '@angular/router-deprecated'
import {APP_BASE_HREF} from '@angular/common'
import {SomeCoolComponent} from './SomeCoolComponent'
@Component({
	selector: 'app',
	templateUrl: 'client/app.html',
	directives: [ROUTER_DIRECTIVES]
})
@RouteConfig([
	{ path: '/', as: 'SomeCoolComponent', component: SomeCoolComponent }
])
class App{

}

let appProviders = [ROUTER_PROVIDERS,provide(APP_BASE_HREF,{useValue: '/'})]
bootstrap(App, appProviders)

When the app start gives me this error:
Uncaught (in promise): No Directive annotation found on SomeCoolComponent

Well, so i've imported RouterLink on SomeCoolComponent, just to check... and the error has changed to:
Uncaught Cannot resolve all parameters for 'RouteRegistry'(?). Make sure that all the parameters are decorated with Inject or have valid type annotations and that 'RouteRegistry' is decorated with Injectable.

Did you add RouterLink into Component directives?
import { Component } from '@angular/core';
import { RouterLink } from '@angular/router-deprecated';

@Component({
    selector: 'eg-cool',
    directives: [RouterLink], // REVIEW: `RouterLink` Added?
    templateUrl: '/client/imports/cool/cool.html'
})
export class SomeCoolComponent { }

Try to import ROUTER_DIRECTIVES on SomeCoolComponent

@barbatus  @derek-fong Sorry but isn't working. Still getting "Uncaught Cannot resolve all parameters for 'RouteRegistry'(?). Make sure that all the parameters are decorated with Inject or have valid type annotations and that 'RouteRegistry' is decorated with Injectable. - reflective_provider.js:182"

@insidemybrain this issue is certainly not related to this repo. Here is resources where you can ask questions https://github.com/Urigo/angular2-meteor#questions-and-issues, also the error message itself is quite verbosely saying about the possible origin


Implement batch CLI with batch service

We did the short cut in #2203, ideally we want to host a batch service so that batch job can be triggered programmingly

We did the short cut in https://github.com/uber/cadence/pull/2203

Grabbing this.


Inline container precedence with attributes

In e.g. djot.js:
*{a="*"}

yields

*

while
*{a="*"

yields

{a=””

The general inline precedence rule suggests that "the first opener that gets
closed takes precedence". In this case, however, the attributes have precedence
even though they are closed after the * is closed.
The first goal of djot is to allow parsing without backtracking, but is this
case really possible to parse this way without any backtracking? When
encountering the second *, we have to consider two possible outcomes:

the attributes are closed later and we should ignore the *, or
the attributes are not closed later and we must close the *.

How to handle this specific case isn't really specified in the syntax
reference. The djot.js behavior is probably more user-friendly than following the
general rule, as one would not expect quoted symbols to have impact. But from
an implementation point of view it seems difficult to prioritize attributes while
allowing arbitrary content in quoted attribute values without using backtracking.
Not sure whether it is intentional or not, but djot.js does not seem to allow
completely arbitrary content within the quotes, e.g.
*{a=[txt](url)

turns into

*{a=“[txt](url)

instead of

*{a=txt

The rules you're quoting are said to cover "precedence for inline containers."  The way I was thinking of it, that excludes things like code spans and attributes.  These have precedence over inline containers.  In a full spec, all of this would need to be spelled out more explicitly.
Maybe the other issue is now fixed? With the latest in main I'm getting:
% ./djot
*{a=[txt](url)

*{a=txt

The rules you're quoting are said to cover "precedence for inline containers." The way I was thinking of it, that excludes things like code spans and attributes. These have precedence over inline containers. In a full spec, all of this would need to be spelled out more explicitly.

Yes, and this precedence is probably the better alternative, but it does requires backtracking to parse. You have to parse for attributes first, and if it fails you have to go back and parse everything again. But I guess it should still be parsable in linear time, it is not really possible to nest arbitrarily many attributes within each other (trying to open another quote/comment will close the previous one).

Maybe the other issue is now fixed? With the latest in main I'm getting:
% ./djot
*{a=[txt](url)

*{a=txt

I think I accidentally typed the example without quotes. With quotes it still parses as text on the main branch:
% ./djot
*{a="[txt](url)

*{a=“[txt](url)


Missing EncodingError for Symbol literal with invalid encoding

Looks like CRuby checks this at parsing time:
ruby -c -e ':"\xC3"'
ruby: invalid symbol in encoding UTF-8 :"\xC3" (EncodingError)

This also caused some IRB tests to fail: https://github.com/ruby/irb/pull/854
Also some occurrences in ruby/spec and test-all mentioned by @enebo in #2472.

@eregon @andrykonchin Of course it would be nice if this is fixed but it is worked around pretty easily by just doing a CR scan and look for broken.  Then you can remove those omit's and when it is fixed only delete something from your own source.

This should be fixed on main.


[TW] Research about the number card, we need the card to be shown on the mobile app

Finalize the flow with Discuss to pak pur


Fix random string sef fault issue in array_value_test [#340]

Avoid generating a rand string with len = 0

Coverage decreased (-0.2%) to 52.916% when pulling 1950a8517f964aef1fbe6cc2fa42326a3270231f on eric-haibin-lin:val-test-fix into 6aa7f1c8b909300318848efed61d000989a11e36 on cmu-db:master.


feat: add list example.

It takes a single argument to a file and lists all tags it finds in it, and is taken directly from the README
with the modification of taking an argument.
I thought it would be useful to have in order to quickly see which file formats the library can read or
if it works for the files one might have at hand for integration into an audio-processing workflow.
Please feel free to close without comment if there are no examples for a reason, I just thought I'd contribute
this 'tool' as it was helpful to me :).

Thanks! But I think having the example in the readme is sufficient


Is this project still being maintained?

If not, what are the recommended alternatives?
Thanks!

Never mind, I have found the mailgun implementation.


How much memory is needed?

My GPU is 12g and still out of memory.

Hi, currently, it requires around 14~15 GB GPU memory.
I will continue to improve the memory efficiency.

I am happy to hear you are continuing to improve the memory efficiency.
When could we expect a version with improved memory efficiency?

@zewei-Zhang @MarkWijkhuizen Hi, I finally got time to look into the code.
Now if you're dragging an input real image, you should be able to do it under 12GB GPU memory with 512x512 images.
However, for dragging an 512x512 generated images, it still requires about 13GB memory.
I'll keep try to reduce the memory usage in the future.


WIP: AVX2 Float 32x32 SP

Submitting to get feedback on the blocking sizes. Thanks!

Following changes in this  [6679b23] commit:

Incorporated @alheinecke  feedback.
Removed C++ styled comments.
Tested  I16I32, USI8I32, SUI8I32, SUI8UI8 for NN_EQLD sizes.
BF16F32, BF16, BF1632_FLAT, BF16_FLAT works for sizes <= 32x32.

Next Steps:

I16I32, USI8I32, SUI8I32, SUI8UI8  datatypes needs to be tested for following use case:

NN_GTLD
NT_EQLD
NT_GTLD

Enable BF16 for sizes BF16F32, BF16, BF1632_FLAT, BF16_FLAT >32x32 and fix masking issues.

Closing this pull request, Thanks for the feedback!


Allow running integrated-devnet with Rust VM

Users should be able to specify which VM they want.
The env var needs to be passed: https://shard-labs.github.io/starknet-devnet/docs/guide/run#run-with-the-rust-implementation-of-cairo-vm
This should be simply implementable for both dockerized and installed integrated-devnet.

I started working on this issue today.


Add autocommand test

Crap, running into some problems here. It works on my machine, but my machine is much faster than Travis' workers. And I'd hate to just increase the sleep here... Any ideas?

Maybe there is some way you can call a function to stop all of the jobs, so they will exit earlier.

I'm not familiar enough with the async API to implement that. If you have any bright ideas, go ahead, otherwise, might just have to sleep 5 for this to work.

I'll see what I can dig up from the documentation later this evening.

After reading the documentation, I think the best two options would be to either increase the sleep time, which isn't fantastic, or to expose the script function so you can call it directly. If you dig through Google, there is some discussion of running script functions in Vader, but it involves parsing the source files and might not be the best.

How about a blocking version? We can test ale#Lint seperately by mocking the engine, and we can mock ale#Lint with a blocking version to test the engine.

The best bet is to probably call HandleExit directly and test that.

I have a possible solution for you now. I just added a test which checks that the loclist gets updated after linting is done, and I now use a call for a new function like so:
call ale#engine#WaitForJobs(2000)

That will wait up to 2 seconds for linters to finish their work, but possibly complete sooner than that if jobs are done. So far it seems to work. Adjustments might be needed later if some problems come up around how execution of handlers after jobs finish works.

That sound perfect! I'll go ahead and try to incorporate this now.

Looks like that code only works under Vim 8, not NeoVim. I'm getting an unknown function, job_status.

Regardless, the tests pass in regular Vim. I am having the loclist test fail on my machine though (in Docker).
  Starting Vader: /testplugin/test/test_linting_updates_loclist.vader
    (1/1) [  GIVEN] Some JavaScript with problems
    (1/1) [EXECUTE] The loclist should be updated after linting is done
    (1/1) [EXECUTE] (X) {} should be equal to {'3': [{'lnum': 1, 'bufnr': 3, 'vcol': 0, 'linter_name': 'eslint', 'nr': -1, 'type': 'W', 'col': 10, 'text': 'Infix operators must be spaced. (space-infix-ops)'}, {'lnum': 2, 'bufnr': 3, 'vcol': 0, 'linter_name': 'eslint', 'nr': -1, 'type': 'E', 'col': 10, 'text': 'Missing semicolon. (semi)'}]}
  Success/Total: 0/1

Ah, looks like that was a matter of pulling down the latest docker image. My bad.

It doesn't yet work in NeoVim or on non Unix machines. I'll see what I can do about that.
I think there's a problem with the Makefile where it doesn't know how to pull a more recent build of the Docker image if you already have some older image. I'm not sure how to fix that. Maybe an ID can be written into the Makefile to check against, so that pulling again with a new ID will cause the new image to be loaded.

There's one more thing I just noticed. Could you unlet the g:success variable in an After block so that variable isn't around for other tests? One unfortunate side effect of this is that the variable won't be available by the time the Then block is run, so you'll have to move the assertion into the Execute block. I don't know why Vader runs After before Then. Maybe there's a better way to handle this.

Thanks for adding the test! I'll mark this one off on the ongoing issue.