Additional: I just turned on allowing apps from anywhere (System Prefs > Security & Privacy > General > Allow apps downloaded from... > Anywhere), then let the Verify process run and run. After 20 minutes, it finally finished...and said I couldn't launch Chromium because it's from an unverified developer — even though I'd allowed aps from anywhere, and even though I've been downloading Chromium updates through the official channel (via the browser extension taking me to SourceForge) with no problems for years and years.

Thanks for the issue...

Tried to reproduce the issue on reported chromium 70.0.3538.102 using Mac 10.14.0 and 10.12.6. attaching screencast for reference.
Steps:
-----
1. Downloaded latest Chromium  
2. Opened DMG and drag Chromium into Applications
3. Clicked on chromium 
As we have observed that the Chromium launches without dialog "Verifying Chromium".

@Reporter: Could you please check the attached screen cast and let us know if anything missed from our end and also confirm that the issue specific to Mac 10.11.6.

Thanks..!

Deleted: 906221.mp4 2.6 MB

	906221.mp4 2.6 MB View Download

Video doesn't show that this is a freshly-updated/freshly-installed build 70.0.3538.102, but I'll assume it is.

I cannot confirm its specific fo 10.11.6 because I don't have ready access to a Mac running a newer OS.

HOWEVER, I do have some new details and a new symptom:

- After several attempts, I was able to get Chromium to open without the "unverified developer" prompt, but now when it launches, I get a brief flash of a small window with the title "Profile error occurred" (see attached). After this flashes on the screen, Chromium launches normally.

Was prompted today that there's another new build. I'm afraid to even try.

Deleted: Chromium - Profile error occurred.png 1.7 MB

	Chromium - Profile error occurred.png 1.7 MB View Download

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Retried the issue on reported chrome version #70.0.3538.102 using Mac OS 10.13.6 by following steps as per comment#0 and comment#5. After dragging the dmg file to application, observed that chromium launched without any errors.

Attached the screencast for reference.
@reporter: Could you please review attached screencast and let us know if anything is being missed here.
Thanks.!

Deleted: 906221.mp4 4.1 MB

	906221.mp4 4.1 MB View Download

Just attempted to launch 70.0.3538.110, and I'm still having the same problem. Video attached — but I stopped recording part way through because I figure you didn't want to watch 5-6 minutes of "Verifying Chromium" and the Chromium icon bouncing in the Dock.
At the end of the 5-6 minutes, I get the "can't be opened because it's from an unidentified developer" (screenshot of that also attached).

I've considered saving my profiles from Application Support > Chromium, then uninstalling Chromium completely and reinstalling. But if it the same thing happens, I'm screwed, so...hesitant to try it.

Deleted: verifying chromium failed.png 36.3 KB

	verifying chromium failed.png 36.3 KB View Download

Dang it. I attached a video! Trying again...

Deleted: verifying chromium.mp4 4.1 MB

	verifying chromium.mp4 4.1 MB View Download

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

FYI, I've just rebooted, then turned on "Allow apps downloaded from: Anywhere" in system prefs, then launched Chromium again. Still took 5-6 minutes of "Verifying Chromium," then finally did ask if I wanted to open it even though it's from the internet. Said yes, then...nothing. Chromium stopped bouncing in the dock, but did not launch. Now when I try to launch it, nothing happens. Can't launch from the dock (bounces once, then nothing happens), can't launch by double-clicking in Applications. Can't launch from Spotlight.

Tested the issue on latest stable chromium #70.0.3538.110, successfully launched the chromium. As per comment#3 and comment#7 unable to reproduce the issue from TE-end, hence requesting someone from 	Internals>Installer team to look into the issue.

Thanks.!

Does Google Chrome have this issue? The build of Chromium your video shows is not one we produce or distribute.

Google Chrome updates automatically in the background, so no, it does not have this issue.

The build of Chromium I'm using is from the same source I've been getting it from for years: The SourceForge page linked from the FreeSMUG Updater extension (https://chrome.google.com/webstore/detail/freesmug-updater-for-chro/ccgjmadhdidfloacagcnnodbkedkjedg), which notifies me when there's a new Chromium build.

Should I be getting it from elsewhere? If so, how should I know when there are new builds available?

I've just looked at the video in Comment 7 again, and it looks to me like the same source as the one in my video in Comment 9. Am I missing something? When you say in Comment 13 that "The build of Chromium your video shows is not one we produce or distribute," how is this being determined?

BTW, I've never been able to find a download page for Chroumium at https://www.chromium.org/Home, except for the raw build at https://download-chromium.appspot.com/.

Sorry to keep adding comments one atop another, but since Comment 13 implied that the build I'm using is not distributed by this team, I just downloaded the raw build from https://download-chromium.appspot.com/ and the problem persists.

Let me know what info I might be able to provide to help.

I'm willing to uninstall completely (including Preferences and Application Support files) and reinstall too, if I can learn how to make sure all my profiles can be preserved/restored.

The Chromium team doesn't ship any official builds at all; anything calling itself "Chromium" that you can download and run isn't something we provide. In particular, I don't think the builds on <https://download-chromium.appspot.com/> are supposed to have release code signatures, since they are only used by developers. The build you have is also not something we support.

The short version is that we probably aren't going to be usefully able to help debug this, since we don't support running either of the builds you're trying to run. Sorry :\

I'm getting mixes messages here: swarnasree.mukkala@chromium.org puts up a screencast showing installation of the exact exact same build from the exact same source in Comment 7, then in Comment 17, ellyjo...@chromium.org tell me the build I have is "not something we support."

So if the version I have is not supported when reporting to bugs.chromium.org, why is someone WITH A CHROMIUM.ORG address uploading videos showing the proper installing of that SAME VERSION? And if the version I have is not supported, where do I find a version that is supported here? There's not much point in reporting bugs if I'm told the version of Chromium about which I'm reporting them isn't recognized as a valid version of the software.

Also, I'm not doing anything differently now than I've ever done with Chromium, which I have been using for at least 5 years.

I do understand that you're apparently unable to recreate the bug, and I do understand that this forum isn't a Chromium "help desk," and I do understand that Chromium is, by its very nature, forever in beta. But on every previous occasion when I've reported Chromium bugs, I've worked with the team here to find a solution — which is what I'd like to do now.

As I've said a couple times upthread, I'm willing to uninstall and reinstall, if the consensus is that this problem is isolated to me. I'd just like to know the best way to go about preserving and restoring my multiple user profiles if I do. Can I just pull out the Profile directories from Application Support > Chromium, uninstall everything else (using AppCleaner to make sure all the remnants are gone), reinstall from scratch, and put those profiles back in Application Support > Chromium? Or do I also need to preserve a .plist or something like that to make the fresh install recognize them?

Should I maybe try installing the newest build in Safe Mode? Or from a different user account on the computer?

The person in #7 is just trying to recreate the bug identically with the steps you provided. I and Elly are saying that these builds of Chromium are not produced by the Chromium project and that there are no supported builds of Chromium - they are for development purposes only. Google Chrome is the official supported product, but bugs that repro consistently between Chromium and Chrome are valid here.

The user data for Chromium is stored in ~/Library/Application Support/Chromium. If you preserve that dir your data should be fine (just do not try to use a profile from any newer version in any older version).

As I noted in  issue 852720 , I think this is something specific to the machine. One possibility is the Gatekeeper database is corrupt. It can be reset by doing `sudo spctl --reset-default` and then rebooting. If that doesn't work, I don't really have other ideas other than trying a macOS upgrade.

Thanks. I'll try an uninstall/reinstall and hope for the best.