the environment doesn't support custom tool name on login screen. upgrade the environment to publish the module. When I double click on this error, it shows an error message in the 'GetUnifiedLoginURL' server action.
Can someone please help to solve this error?
Hi Krishnnambal,
I'm not sure, but it probably has to do with the SEO feature for Reactive Web Apps.
Make sure you upgrade your personal environment to the latest version (11.14.0), which is one of the prerequisites to use the feature.
And also install the latest version of Service Studio (11.13.0 or later is required).
Hope this helps!
Regards,
Nordin
Now I know it has nothing to do with the SEO feature for Reactive Web Apps. The error is due to a new feature that improves the authentication mechanism that is used in our applications.
I can now confirm the error will go away if you upgrade your environment to platform server version 11.14.0 since it's a requirement to use that new feature.
Can you try to upgrade your personal environment to the latest version Krishnnambal and report back here?
Thanks,
We've just hit the same problem, having upgraded our Dev environment to 11.14.0, but our Test environment has not yet been upgraded. Thus we can't publish apps to Test that use the GetUnifiedLoginURL server action from Users.
It appears to be due to the new optional parameter ToolName that has been added to GetUnifiedLoginURL. This is an optional parameter which has no description, so I'm not sure of its purpose?
I think it is poor practice from Outsystems not to flag this up as a Breaking Change in the Release Notes. Sure the problem will go away when we upgrade all of our environments to the same level, but it is common practice to not do this immediately, and to not be able to publish apps in the meantime is a big issue.
Sorry for the Necro...
I could not agree more Darren!!!!
OutSystems are doing the same/similar thing with Service Center [EDIT: Service Studio not Service Center]. Forcing adoption of their upgrades on test groups of users, without warning, knowing that it can cause issues within dev teams if one dev is using a different version of Service Center [EDIT: Service Studio not Service Center] than others.
This specific issue (ToolName) is still causing issues for me and others I help.
Very obstructive and frustrating behaviour from OutSystems!
This is not even picked up by their dependency checking of Forge components before install!
BTW: credit to you for working that out Darren and thank-you for posting!
How can 1 dev use another version of service center than another dev in the same team? Service center is a server side component.
If you are refering to service studio, you can just disable the auto-update feature and stay with whatever version you like.
I do agree however that the toolname issue should have been handled differently.
Good catch Tim, thank-you! :)Yes, I do mean Service Studio, not Service Center.
Separately ... and please understand this frustration is directed at OutSystems, not you Tim.
Basically, the suggestion is, the entire team should turn off auto-update (not that easy by the way, the auto-update checkbox has it's own bugs. I know from experience.), then at some point when things start not working they should all get together and synchronise their update. Then turn auto update off again, then hope the version they landed on doesn't have any major bugs.
Refer back to obstructive and frustrating.
HI All,
Did you have any update on this issue.
BR
A Mohammed Showkath
This bug was still not fixed.
Thanks. Just ran into the same problem. Although development and test is already on version 11.18.1 (Build 37828), production is still stuck on 11.8.4.
Any updates yet?
Everyone is being forced up to Platform version 11.18.1 in the short term (to apply a security fix so middle man attack can’t take over the database). So this issue will resolve itself shortly by virtue of there being no-one left using an older version.
Other than that, this never was a bug, but more of a poorly communicated (if at all) breaking change, that broke semantic versioning as well.
Onwards and upwards to 11.18.1 everyone 🤣