Answer
Since the configuration itself is confirmed correct (it works elsewhere on comparable versions), test the same scenario logged in as the Application Owner in the affected environment before assuming it's a broader bug — if Object Details appears correctly for the Application Owner but not for the regular user, that isolates it to a permission/access gap specific to that environment rather than a genuine functional or version issue with the Object Connection setup itself.