You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently upgraded the heremaps version from 1.23.0 to 1.30.7 and we started to see this error Tangram [error]: Style: error compiling program for style '1_translucent-pattern-lines' in production logs.
I saw the release notes from 1.23.0 upto 1.30.7 to see if missed any breaking changes but there is nothing caught my eyes.
When there is an error the user will see the below image 👇
I cannot able to reproduce this locally with :
Chrome 97.0.4692.71 (Official Build) (x86_64)
macOS 11.4
OR
Chrome 97
Windows 10
Affected users are with version :
Chrome 97, 96 and Windows 10 & 7 combinations.
Edge 97 & Window 10
FF 96 & Window 10
Safari 15 & macOS 10
Open question:
From the release notes I see there is no version for 1.23.0 but when installed it installs the exact version. I assume heremaps 3 has this preceding 3 in front of every release.
This is what we used in our package.json "@here/maps-api-for-javascript": "^1.23.0"
Thanks for such great library 🙂
We recently upgraded the heremaps version from
1.23.0
to1.30.7
and we started to see this errorTangram [error]: Style: error compiling program for style '1_translucent-pattern-lines'
in production logs.I saw the release notes from
1.23.0
upto1.30.7
to see if missed any breaking changes but there is nothing caught my eyes.When there is an error the user will see the below image 👇
I cannot able to reproduce this locally with :
Chrome 97.0.4692.71 (Official Build) (x86_64)
macOS 11.4
OR
Chrome 97
Windows 10
Affected users are with version :
Open question:
From the release notes I see there is no version for
1.23.0
but when installed it installs the exact version. I assume heremaps 3 has this preceding3
in front of every release.This is what we used in our package.json
"@here/maps-api-for-javascript": "^1.23.0"
Full Log:
Possibly related to #63 ?
The text was updated successfully, but these errors were encountered: