Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update [email protected], should fix all Mac rosetta emulation bugs #285

Closed
jpike88 opened this issue Feb 10, 2022 · 5 comments
Closed

Comments

@jpike88
Copy link

jpike88 commented Feb 10, 2022

related to #272

@ltm
Macs on rosetta emulation have been having segmentation faults when using this library. Pls update sharp, it will fix those issues.

@hdk
Copy link

hdk commented Apr 29, 2022

I just switched to M1-Mac:
OS: macOS 12.3.1
CPU: (10) x64 Apple M1 Pro
node: v12.22.7

updated cordova-res 0.15.4 with [email protected] and @types/[email protected]

still getting segmentation faults!

edit: ran it multiple times - the number of generated files always differs and sometimes I get "illegal hardware instruction" instead of "segmentation fault"

@mlynch
Copy link
Contributor

mlynch commented Oct 2, 2022

Sharp has been updated for the new @capacitor/assets tool

@mlynch mlynch closed this as completed Oct 2, 2022
@estebancastrosola
Copy link

I just switched to M1-Mac: OS: macOS 12.3.1 CPU: (10) x64 Apple M1 Pro node: v12.22.7

updated cordova-res 0.15.4 with [email protected] and @types/[email protected]

still getting segmentation faults!

edit: ran it multiple times - the number of generated files always differs and sometimes I get "illegal hardware instruction" instead of "segmentation fault"

Hello! I have same error couple of days. Could you fix it?

@mlynch
Copy link
Contributor

mlynch commented Nov 22, 2022

@estebancastrosola are you on cordova-res or @capacitor/assets? cordova-res isn't receiving any updates any more, we recommend moving to @capacitor/assets (though this drops Cordova support)

@estebancastrosola
Copy link

Hi there! @mlynch , I have the same issue in boths, I have created a issue where explain better. #443

Thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants