Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Adobe Launch Extension Breaking Calling s.t() and s.tl()

Avatar

Avatar
Level 1
juliazhoululu
Level 1

Likes

0 likes

Total Posts

1 post

Correct Reply

0 solutions
View profile

Avatar
Level 1
juliazhoululu
Level 1

Likes

0 likes

Total Posts

1 post

Correct Reply

0 solutions
View profile
juliazhoululu
Level 1

03-02-2021

While upgrading extensions for an Adobe Launch property, I noticed that any rules based on a Direct Call stopped firing with version 1.9.0. I'm still testing this in a Launch environment, but example of what’s happening:

 

Calling s.tl() and s.t() seems to not be working. The function is defined, but it doesn’t fire the server call.

Screen Shot 2021-02-03 at 10.29.17 AM.png

 

Is this a known issue?

 

Update: This has been resolved, it was caused by another extension.

Accepted Solutions (0)

Answers (1)

Answers (1)

Avatar

Avatar
Springboard
MVP
yuhuisg
MVP

Likes

152 likes

Total Posts

481 posts

Correct Reply

90 solutions
Top badges earned
Springboard
Bedrock
Validate 1
Establish
Contributor
View profile

Avatar
Springboard
MVP
yuhuisg
MVP

Likes

152 likes

Total Posts

481 posts

Correct Reply

90 solutions
Top badges earned
Springboard
Bedrock
Validate 1
Establish
Contributor
View profile
yuhuisg
MVP

03-02-2021

While I get the same console logging result as you, I can verify that my Custom Links beacons are still being sent with Direct Call events as expected. (I verified using the Adobe Debugger browser extension.)