SDK Update 60 -> 63/64: Error encountered. Aborting

Hi there,

I'm wondering if anyone tried to update to the latest SDK (63 or 64)?
The thing is that we are trying to update it from version 60.0.732-1.4.2-2 to version 63.0.741-1.4.2-2 or 64.0.744-1.4.2-2, however, the process interrupts on "Starting 'app-icons-android' with the error "Error encountered. Aborting!".

It happens when updating the app (./sdk init-native) as well as when generating a new one ($SUGAR_MOBILE_SDK_HOME/<version>/sdk/generate-app).

Homebrew and node are updated to the latest version
jdk-11.0.19

There is no further explanation in the logs, only "Error encountered. Aborting!".

Has anyone run into the same problem and maybe addressed it?

Thank you.

Parents

0 Eugene Bychkov over 2 years ago

Anastasiia Gubanovych could you please provide exact command that you are executing to generate an app?
i am specifically interested if there are any params provided to generate-app script

also

please try to run:

cd $SUGAR_MOBILE_SDK_HOME/64.0.744-1.4.2-2

./sdk/generate-app

does it work for you?
0 Anastasiia Gubanovych over 2 years ago in reply to Eugene Bychkov

Hi Eugene Bychkov ,

As per the command to generate an app - there are no params.
For the new app:
$SUGAR_MOBILE_SDK_HOME/64.0.744-1.4.2-2/sdk/generate-app

For the updating from the previous sdk version:
cd mobileapp
./sdk init-native

We tried to run the command you suggested, but unfortunately, the result is the same:
0 Eugene Bychkov over 2 years ago in reply to Anastasiia Gubanovych

got it

what are your current node version and java versions?

are you on Linux os?

also it would be helpful if you attached all terminal logs starting from ./generate-app invocation
0 Anastasiia Gubanovych over 2 years ago in reply to Eugene Bychkov

node v21.1.0
Homebrew 4.1.19
yarn 1.22.19
jdk-11.0.19

Linux, yes (debian 12)

Attaching logs:
logs.txt
0 Eugene Bychkov over 2 years ago in reply to Anastasiia Gubanovych

tried your command and it worked well for me

i am on Mac though
i suggest following

please try

1. remove node_modules folder (rm -rf node_modules)

2. switch to node v18.16.0 (this version will be used during generate-app script)

3. yarn install to install modules under this node version

4. completely remove folder with existing app (invocation)

5. run generate-app again

if it doesn't help i suggest trying the same with java version 18
0 Eugene Bychkov over 1 year ago in reply to Eugene Bychkov

Anastasiia Gubanovych I wonder if it did help?
0 Anastasiia Gubanovych over 1 year ago in reply to Eugene Bychkov

Hi Eugene Bychkov ,

Unfortunately, the result is the same. We tried the steps you described, then the same with Java v18, deployed the environment from scratch with the needed versions (rather than upgrade/downgrade them) - nothing worked

Are there any other options/tips we could try?
0 Eugene Bychkov over 1 year ago in reply to Anastasiia Gubanovych

i suspect one of the new node modules that was introduces maybe incompatible with your environment

let's confirm this

1. please check sdk version 60 again on your current environment. does it work now?

2. switch to v64 and rm -rf node_modules and do npm install. check logs , were all modules installed successfully?

i suspect maybe issue related to linux? meanwhile we will check if we can improve logging of the problem on our side
0 Eugene Bychkov over 1 year ago in reply to Eugene Bychkov

Anastasiia Gubanovych any news?
0 Anastasiia Gubanovych over 1 year ago in reply to Eugene Bychkov

Hi Eugene Bychkov ,

Sorry for the delay - but no good news so far:

1 - yes
2 - no errors in logs related to node_modules, looks ok

We tried Ubuntu, behavior was the same

Some additional logging would be a great help in locating where the issue is.

Reply

0 Anastasiia Gubanovych over 1 year ago in reply to Eugene Bychkov

Hi Eugene Bychkov ,

Sorry for the delay - but no good news so far:

1 - yes
2 - no errors in logs related to node_modules, looks ok

We tried Ubuntu, behavior was the same

Some additional logging would be a great help in locating where the issue is.

Children

0 Eugene Bychkov over 1 year ago in reply to Anastasiia Gubanovych

I'll give you some tips how you can debug failing script on your machine

1. after you have encountered this error you will have {yourapp} or {yourapp}/Sample folder created. from this folder copy 'config' folder to you sdk installation folder

2. in your sdk install folder you have a gulp task named 'app-icons-android' that seems to be failing. this is essentially a node process that you need to debug

here is my VSCode run configuration to do this (this is an equivalent of './gulp app-icons-android' console command)

{

"name": "Run a gulp task",

"type": "node",

"request": "launch",

"program": "${workspaceRoot}/node_modules/gulp/bin/gulp.js",

"stopOnEntry": false,

"args": ["app-icons-android"],

"cwd": "${workspaceRoot}",

// "runtimeArgs": [

// "--nolazy"

// ],

"console": "internalConsole"

},

3. put a breakpoint into app-icons.mjs and from here you can debug your error

i hope this helps!
0 Sergey Kurgansky over 1 year ago in reply to Anastasiia Gubanovych

Hi Anastasiia Gubanovych, Have you manage to run app-icon-android task as Eugene suggested? I think there could be an issue with library we used for that task. It's called sharp. https://www.npmjs.com/package/sharp that one. Documentation says that "Most modern macOS, Windows and Linux systems do not require any additional install or runtime dependencies." but that doesn't mean all.

Please run that app-icons-android gulp task, it could give more information related to the problem.
0 Anastasiia Gubanovych over 1 year ago in reply to Sergey Kurgansky

Hi Sergey Kurgansky , Eugene Bychkov ,

Thank you for your suggestions - indeed the problem is in importing 'sharp' library.
Though it is not clear what exactly is wrong with it - it looks like the needed relationships are there and the library itself is in SDK files.

Would you please suggest how we could fix it?
0 Sergey Kurgansky over 1 year ago in reply to Anastasiia Gubanovych

Hi Anastasiia Gubanovych

I would try to run some code samples from sharp repo or internet. Does it work?

If no then go though docs on sharp library

sharp.pixelplumbing.com/install

https://sharp.pixelplumbing.com/install#cross-platform

This library might need some other dependancies to be preinstalled on your machine. This should be described in docs

You can also try to upgrade its (sharp) version on your side using package.json if bundled version doesn't work on your side.

Hope it helps