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 have an experience for the app that display a modal to the user to collect specific optin. The user can either :
closed the modal -> slide the modal to close
accept and close -> when clicking this option, the template send a request to update a custom field and then send a postMessage to the parent to trigger the closing function
Issue
A short while ago, we're not sure since when exactly, we noticed that the template base url changed and was different between IOS and Android. It changed from "https://buy-eu.piano.io" to "https://api-eu.piano.io".
This can be worked around by creating different templates for IOS and Android, but it also impacted the custom field update.
The request base url, we use, is the following : "https://experience-eu.piano.io/".
We also worked around that second issue, by forcing the "https://buy-eu.piano.io" on to the templates displayed on IOS.
Questions
Is there an explanation on why the template base url have an impact on a request with a different base url inside a Piano template ?
Why did the template base url changed ?
The text was updated successfully, but these errors were encountered:
Context
We have an experience for the app that display a modal to the user to collect specific optin. The user can either :
Issue
A short while ago, we're not sure since when exactly, we noticed that the template base url changed and was different between IOS and Android. It changed from "https://buy-eu.piano.io" to "https://api-eu.piano.io".
This can be worked around by creating different templates for IOS and Android, but it also impacted the custom field update.
The request base url, we use, is the following : "https://experience-eu.piano.io/".
We also worked around that second issue, by forcing the "https://buy-eu.piano.io" on to the templates displayed on IOS.
Questions
The text was updated successfully, but these errors were encountered: