dyld: lazy symbol binding failed: Symbol not found: __Z18sse42_is_availablev with version 9.8.0

[palkerecsenyi]

[REQUIRED] Environment info

firebase-tools: 9.8.0

Platform: macOS (Apple M1)

NodeJS: 15.12.0

[REQUIRED] Test case

Any Firebase Functions project

[REQUIRED] Steps to reproduce

Run this command:

firebase deploy --only functions

[REQUIRED] Expected behavior

I'd expect it to deploy my functions as normal. It works perfectly with version 9.7.0 and below, but 9.8.0 breaks it.

[REQUIRED] Actual behavior

dyld: lazy symbol binding failed: Symbol not found: __Z18sse42_is_availablev
  Referenced from: /Users/palkerecsenyi/.nvm/versions/node/v15.12.0/lib/node_modules/firebase-tools/node_modules/sse4_crc32/build/Release/crc32c.node
  Expected in: flat namespace

dyld: Symbol not found: __Z18sse42_is_availablev
  Referenced from: /Users/palkerecsenyi/.nvm/versions/node/v15.12.0/lib/node_modules/firebase-tools/node_modules/sse4_crc32/build/Release/crc32c.node
  Expected in: flat namespace

zsh: abort      firebase deploy --only functions:<redacted>,functions:<redacted>

[tiny-dancer]

https://stackoverflow.com/questions/66816456/firebase-broken-on-m1-mac

which firebase-tools do you have? had the same issue with 9.8.0 - downgrading to 9.7.0 made it work – RandomDude yesterday

[robinpdev]

Had this exact issue too, i guess firebase QA needs some waking up.

[tiny-dancer]

Some new equipment :)

[samtstern]

@robinpdev please be respectful when commenting here!

[robinpdev]

@samtstern Sorry if that offensive, still love firebase🔥

[samtstern]

@palkerecsenyi thanks for reporting this, we've had a few issues with M1 macs and especially with Node 15. Unfortunately since we've all been working from home during the pandemic nobody on our team has been able to get a new laptop for work so we don't have good M1 test coverage and GitHub actions (where we do our CI testing) doesn't have ARM or M1 options.

I'll report this to some team members who may have bought their own M1 machines and see if they can reproduce it.

[miketrebilcock]

Looks like the addition of fast-crc32c within the emulators created the problem in 9.8.0. v9.7.0...v9.8.0#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519

[samtstern]

@miketrebilcock thanks for pointing that out! I bet you're right.

[wiesson]

I'm not sure, but it looks like this package does compile natively https://github.com/napi-rs/node-rs/tree/main/packages/crc32 and could replace fast-crc32c 🤔

[bradleymackey]

Just a heads up that I'm also seeing this issue on armv7l on a Raspberry Pi.

[fernandolguevara]

@mbleigh, @ taeold can you release a version with this fix ? please?