We are noticing that a lot of our users seem to hit a "network request failed" when bringing the at.js file into a React web application:
This is a screenshot of the error we are detecting. What is the typical cause of this? Can it be security settings on the browser? Is there a workaround?
Solved! Go to Solution.
Hello,
at.js can be accessed from any application or website until unless it has supported environment setup and has authorized setting related to account.
now, can you plz share more details...
1. can you share network log or console error
2. where is your at.js file located and how you are referring at.js in react app??
3. who is your user, is it internal users (inside vpn) or your end user?
thanks!!
Hi @jchabot86 are you connected with some proxy ?
can you try checking this with some open network ?
Hello,
at.js can be accessed from any application or website until unless it has supported environment setup and has authorized setting related to account.
now, can you plz share more details...
1. can you share network log or console error
2. where is your at.js file located and how you are referring at.js in react app??
3. who is your user, is it internal users (inside vpn) or your end user?
thanks!!
Personally, I do not get the error, but a lot of our end users do seem to get the error. Unfortunately, I am unable to get their actual console logs.
A realtime user monitoring tool we use is detecting that this error is occurring for multiple users.
2. where is your at.js file located and how you are referring at.js in react app??
Loading of script (from public folder)/targetpageParams:
Function to execute getOffer()
3. who is your user, is it internal users (inside vpn) or your end user?
End user - we don't have direct contact with our end users unfortunately.
If the above code looks good - then I'm looking for tips/advice as to what is the probable cause of this issue.
To add onto that, if I run Firefox in "strict" mode: I am able to replicate it:
Personally, I do not get the error, but a lot of our end users do seem to get the error. Unfortunately, I am unable to get their actual console logs. A realtime user monitoring tool we use is detecting that this error is occurring for multiple users.
2. where is your at.js file located and how you are referring at.js in react app??
Loading of script (from public folder)/targetpageParams:
Function to execute getOffer()
3. who is your user, is it internal users (inside vpn) or your end user?
End user - we don't have direct contact with our end users unfortunately.
If the above code looks good - then I'm looking for tips/advice as to what is the probable cause of this issue.
Hi @Pawan-Gupta and @ambikaTewari_ATCI! Thank you both for reaching out here with some clarifying questions! Do you have any further thoughts on @jchabot86 's additional context?
Warmly,
Amelia, your Adobe Target Community Manager
Views
Replies
Total Likes
Views
Likes
Replies