Timeline for Managed Package: Updating Connected App callback url on packaging org after release
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 27, 2019 at 10:12 | comment | added | Mohith Shrivastava | The second behavior I am familiar but first one to me is bit weird one .I suggest you raise a case so Salesforce is aware of it and documents it in better terms . | |
| Dec 27, 2019 at 8:57 | comment | added | wesaw | The docs are very vague about this. From what we've tested, it's right the opposite case, i.e. just updating callback url on packaging org (even without releasing a beta version) makes existent integration on subscriber orgs fail with an error like 'callback url does not match'. Another interesting use case we've tested - you can create new connected app in a packaging org (without even including it in a package itself), and then you can configure existent subscribers with this app keys and integration just works. Seems like packaging org hosts/owns connected app, but not a package version. | |
| Dec 27, 2019 at 8:25 | history | answered | Mohith Shrivastava | CC BY-SA 4.0 |