(In reply to Nick Alexander :nalexander [he/him] from comment #2) > This looks like `UpdRootD` is in `GreD`, which on newer macOS will never work. On my Firefox Nightly, `UpdRootD` is > ``` > /Users/nalexander/Library/Caches/Mozilla/updates/Applications/Firefox Nightly > ``` Is it? Comment 0 says: > In this case, I suspect the update log files and extension listed below were causing the signature check to fail resulting in the launch failure. The update directory from the *Troubleshooting Information* page was reported as `/Users/mconley/Library/Caches/Thunderbird/updates/Applications/Thunderbird`. But clearly update files are ending up in the update bundle and I'm not really sure how. Maybe a previous version wrote update data there and it never actually gets removed on update? --- (In reply to Haik Aftandilian [:haik] from comment #3) > For both apps, checking users of XRE_UPDATE_ROOT_DIR, and the docs for it [here](https://searchfox.org/comm-central/rev/7340134fa7d638f1a580c7855e33a66a27d9c94a/mozilla/xpcom/build/nsXULAppAPI.h#150-168), when we fail to get XRE_UPDATE_ROOT_DIR, we fallback to using the app dir as the update dir. If that's what is happening here, the question would be what would cause us to fail to get XRE_UPDATE_ROOT_DIR. I see that that comment suggests that we ought to do that (and that comment should be updated because we really shouldn't do that on macOS). But it [doesn't look to me](https://searchfox.org/comm-central/rev/c58bfdfa19b54597373ef699d595e857111545ab/mozilla/toolkit/mozapps/update/UpdateService.sys.mjs#1045-1054) like we actually do that.
Bug 1851948 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Nick Alexander :nalexander [he/him] from comment #2) > This looks like `UpdRootD` is in `GreD`, which on newer macOS will never work. On my Firefox Nightly, `UpdRootD` is > ``` > /Users/nalexander/Library/Caches/Mozilla/updates/Applications/Firefox Nightly > ``` Is it? Comment 0 says: > The update directory from the *Troubleshooting Information* page was reported as `/Users/mconley/Library/Caches/Thunderbird/updates/Applications/Thunderbird`. But clearly update files are ending up in the update bundle and I'm not really sure how. Maybe a previous version wrote update data there and it never actually gets removed on update? --- (In reply to Haik Aftandilian [:haik] from comment #3) > For both apps, checking users of XRE_UPDATE_ROOT_DIR, and the docs for it [here](https://searchfox.org/comm-central/rev/7340134fa7d638f1a580c7855e33a66a27d9c94a/mozilla/xpcom/build/nsXULAppAPI.h#150-168), when we fail to get XRE_UPDATE_ROOT_DIR, we fallback to using the app dir as the update dir. If that's what is happening here, the question would be what would cause us to fail to get XRE_UPDATE_ROOT_DIR. I see that that comment suggests that we ought to do that (and that comment should be updated because we really shouldn't do that on macOS). But it [doesn't look to me](https://searchfox.org/comm-central/rev/c58bfdfa19b54597373ef699d595e857111545ab/mozilla/toolkit/mozapps/update/UpdateService.sys.mjs#1045-1054) like we actually do that.
(In reply to Nick Alexander :nalexander [he/him] from comment #2) > This looks like `UpdRootD` is in `GreD`, which on newer macOS will never work. On my Firefox Nightly, `UpdRootD` is > ``` > /Users/nalexander/Library/Caches/Mozilla/updates/Applications/Firefox Nightly > ``` Is it? Comment 0 says: > The update directory from the *Troubleshooting Information* page was reported as `/Users/mconley/Library/Caches/Thunderbird/updates/Applications/Thunderbird`. But clearly update files are ending up in the app bundle and I'm not really sure how. Maybe a previous version wrote update data there and it never actually gets removed on update? --- (In reply to Haik Aftandilian [:haik] from comment #3) > For both apps, checking users of XRE_UPDATE_ROOT_DIR, and the docs for it [here](https://searchfox.org/comm-central/rev/7340134fa7d638f1a580c7855e33a66a27d9c94a/mozilla/xpcom/build/nsXULAppAPI.h#150-168), when we fail to get XRE_UPDATE_ROOT_DIR, we fallback to using the app dir as the update dir. If that's what is happening here, the question would be what would cause us to fail to get XRE_UPDATE_ROOT_DIR. I see that that comment suggests that we ought to do that (and that comment should be updated because we really shouldn't do that on macOS). But it [doesn't look to me](https://searchfox.org/comm-central/rev/c58bfdfa19b54597373ef699d595e857111545ab/mozilla/toolkit/mozapps/update/UpdateService.sys.mjs#1045-1054) like we actually do that.