Xinyi Ye comments

Results 44 comments of


                                            Xinyi Ye

Sentry Issue: Amplitude Logger [Warn]: Failed to store session replay events in IndexedDB

Hi @ritikaGupta4, could you update to the latest version? We had a fix recently.

TS1005 Error amplitude/analytics-types/element-interaction.ts:70:39 ? expected During Angular build amplitude/analytics-browser version 2.9.3

Hi @RakeshrajA5, is it the same issue as https://github.com/amplitude/Amplitude-TypeScript/issues/882? Could you run `yarn list @amplitude/analytics-types` in your project and share the screenshot? Thanks

TS1005 Error amplitude/analytics-types/element-interaction.ts:70:39 ? expected During Angular build amplitude/analytics-browser version 2.9.3

analytics-browser 2.11.8 and analytics-types 2.8.3 should fix it

fix(uuid): update uuid.ts based on JS implementation

Hi @visiodeibc, TS’s `analytics-core` package is shared by both browser (`analytics-browser` package) and node (`analytics-node` package) environments in which crypto should be imported differently. It's predefined in browser environment but...

Browser SDK 2 initialization error "null is not an object"

@dhruvg, it should be fixed. Could you check again?

Browser SDK 2 initialization error "null is not an object"

Could you provide the url of your website so that I can reproduce?

Browser SDK 2 initialization error "null is not an object"

Could you clear cache and try again? Scripts are stored in cache as well.

"[Amplitude] TypeError: undefined is not an object (evaluating 't._metadataStorage.save')" errors seen on Sentry

Hi @bitttttten, thanks for choosing Amplitude. To further debug this error, we need more info. - How often do you see this error? - Could you provide the website so...

Remote Script Loading in `@amplitude/analytics-browser` Violates Chrome Extension Manifest V3 Policies

Hi, thanks for choosing Amplitude. We are working on a fix for it. For a workaround, please use a version

Remote Script Loading in `@amplitude/analytics-browser` Violates Chrome Extension Manifest V3 Policies

Hi folks, we're planning to fix this in Sept (cc: @Dogfalo). Currently, the workaround is to strip out the URL like this [comment](https://github.com/amplitude/Amplitude-TypeScript/issues/859#issuecomment-2783523139).