Is macOS Mojave not supported anymore? #88419

Closed
opened 2021-05-20 05:20:18 +02:00 by Kuzey · 29 comments

System Information
Operating system: mac OS Mojave 10.14.6 (18G9028)
Graphics card:

Blender Version
blender-2.93.0-beta(May19th build)
blender-3.0.0-alpha (May19th build)
blender-3.0.0-alpha (May20th build)

I haven't tried blender-2.83.15-stable release but I'm thinking it'll be the same.

Short description of error

It looks like macOS Mojave is not supported all of a sudden in the latest builds, I can't launch the program anymore.
blenbend.jpg

Exact steps for others to reproduce the error
Based on the default startup or an attached .blend file (as simple as possible).

**System Information** Operating system: mac OS Mojave 10.14.6 (18G9028) Graphics card: **Blender Version** blender-2.93.0-beta(May19th build) blender-3.0.0-alpha (May19th build) blender-3.0.0-alpha (May20th build) I haven't tried blender-2.83.15-stable release but I'm thinking it'll be the same. **Short description of error** It looks like macOS Mojave is not supported all of a sudden in the latest builds, I can't launch the program anymore. ![blenbend.jpg](https://archive.blender.org/developer/F10128757/blenbend.jpg) **Exact steps for others to reproduce the error** Based on the default startup or an attached .blend file (as simple as possible).
Author

Added subscriber: @kuzey

Added subscriber: @kuzey

#88677 was marked as duplicate of this issue

#88677 was marked as duplicate of this issue

#88444 was marked as duplicate of this issue

#88444 was marked as duplicate of this issue

Added subscriber: @Oxer-1

Added subscriber: @Oxer-1

With the last 2.83.14 on macOS High Sierra 10.13.6 happens the same, not supported.
The Requirements page shows this:

Requeriments.jpg

With the last 2.83.14 on macOS High Sierra 10.13.6 happens the same, not supported. The Requirements page shows this: ![Requeriments.jpg](https://archive.blender.org/developer/F10128786/Requeriments.jpg)

Added subscriber: @NRH_BEATS

Added subscriber: @NRH_BEATS

MacOS? No, thanks.
Yestersday Microsoft released new Win10 21H1 build.
Today i did a clean install, and all works super nice.

MacOS? No, thanks. Yestersday Microsoft released new Win10 21H1 build. Today i did a clean install, and all works super nice.

Added subscriber: @Memento

Added subscriber: @Memento
Author

In #88419#1163214, @Oxer-1 wrote:
With the last 2.83.14 on macOS High Sierra 10.13.6 happens the same, not supported.
The Requirements page shows this:

Requeriments.jpg

Everything was fine up until this week and I remember Pablo Vazquez saying on Blender Today, Apple was responsible for the ARM version. I'm thinking maybe the Apple coders or even Blender coders, fixed/changed something small and it broke compatibility with older OS's?? Hope they fix it soon :)

> In #88419#1163214, @Oxer-1 wrote: > With the last 2.83.14 on macOS High Sierra 10.13.6 happens the same, not supported. > The Requirements page shows this: > > ![Requeriments.jpg](https://archive.blender.org/developer/F10128786/Requeriments.jpg) Everything was fine up until this week and I remember Pablo Vazquez saying on Blender Today, Apple was responsible for the ARM version. I'm thinking maybe the Apple coders or even Blender coders, fixed/changed something small and it broke compatibility with older OS's?? Hope they fix it soon :)
Author

I just noticed the download file names are different...were these complied on a different system or with a new process?

Why is Darwin in the file names?

Anyway, hope it helps
blend6.jpg

I just noticed the download file names are different...were these complied on a different system or with a new process? Why is Darwin in the file names? Anyway, hope it helps ![blend6.jpg](https://archive.blender.org/developer/F10129042/blend6.jpg)
Member

Added subscriber: @ankitm

Added subscriber: @ankitm
Member

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Member

Looks like a bug in platform_apple_xcode.cmake so confirming instead of redirecting to devtalk. CMAKE_OSX_DEPLOYMENT_TARGET is set to builder's OS version and is not corrected to be OSX_MIN_DEPLOYMENT_TARGET.

Is macOS Mojave not supported anymore?

It is supported, requirements have not changed. Will be fixed soon.

I just noticed the download file names are different...were these complied on a different system or with a new process?

Yes, the builder was improved.

Looks like a bug in `platform_apple_xcode.cmake` so confirming instead of redirecting to devtalk. `CMAKE_OSX_DEPLOYMENT_TARGET` is set to builder's OS version and is not corrected to be `OSX_MIN_DEPLOYMENT_TARGET`. >Is macOS Mojave not supported anymore? It is supported, requirements have not changed. Will be fixed soon. > I just noticed the download file names are different...were these complied on a different system or with a new process? Yes, the builder was improved.

Added subscribers: @sebbas, @ponderz

Added subscribers: @sebbas, @ponderz

The legacy and new workers are on Catalina 15.13.7.

As a developer, it might make sense to use that value as current OS. @sebbas would need to confirm this.
As a build worker, via the build pipeline, we might want to configure the specific minimum for the released version and override OSX_MIN_DEPLOYMENT_TARGET.
Otherwise, this change will need to be merged to all supported branches, including experimental and then rebuild.

I would prefer to override CMAKE_OSX_DEPLOYMENT_TARGET via new build pipeline that will apply the value across all branches in case this changes again.

The legacy and new workers are on Catalina 15.13.7. As a developer, it might make sense to use that value as current OS. @sebbas would need to confirm this. As a build worker, via the build pipeline, we might want to configure the specific minimum for the released version and override OSX_MIN_DEPLOYMENT_TARGET. Otherwise, this change will need to be merged to all supported branches, including experimental and then rebuild. I would prefer to override `CMAKE_OSX_DEPLOYMENT_TARGET` via new build pipeline that will apply the value across all branches in case this changes again.

Here is the generated Info.plist file.
Not sure if that value is used.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-*Apple*DTD PLIST 1.0*EN" "http:*www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>LSMinimumSystemVersion</key>
	<string>10.9.0</string>
	<key>CFBundleDocumentTypes</key>
	<array>
		<dict>
			<key>CFBundleTypeExtensions</key>
			<array>
				<string>blend</string>
			</array>
			<key>CFBundleTypeIconFile</key>
			<string>blender file icon.icns</string>
			<key>CFBundleTypeName</key>
			<string>Blender File</string>
			<key>CFBundleTypeOSTypes</key>
			<array>
				<string>BLND</string>
			</array>
			<key>CFBundleTypeRole</key>
			<string>Editor</string>
			<key>LSIsAppleDefaultForType</key>
			<true/>
		</dict>
	</array>
	<key>CFBundleExecutable</key>
	<string>Blender</string>
	<key>CFBundleGetInfoString</key>
	<string>2.83.15 2021-05-19, Blender Foundation</string>
	<key>CFBundleIconFile</key>
	<string>blender icon.icns</string>
	<key>CFBundleIdentifier</key>
	<string>org.blenderfoundation.blender</string>
	<key>CFBundleInfoDictionaryVersion</key>
	<string>6.0</string>
	<key>CFBundleName</key>
	<string>Blender</string>
	<key>CFBundlePackageType</key>
	<string>APPL</string>
	<key>CFBundleShortVersionString</key>
	<string>2.83.15</string>
	<key>CFBundleSignature</key>
	<string>????</string>
	<key>CFBundleVersion</key>
	<string>2.83.15 2021-05-19</string>
	<key>NSPrincipalClass</key>
	<string>NSApplication</string>
	<key>NSHighResolutionCapable</key>
	<true/>
</dict>
</plist>
Here is the generated `Info.plist` file. Not sure if that value is used. ``` <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-*Apple*DTD PLIST 1.0*EN" "http:*www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>LSMinimumSystemVersion</key> <string>10.9.0</string> <key>CFBundleDocumentTypes</key> <array> <dict> <key>CFBundleTypeExtensions</key> <array> <string>blend</string> </array> <key>CFBundleTypeIconFile</key> <string>blender file icon.icns</string> <key>CFBundleTypeName</key> <string>Blender File</string> <key>CFBundleTypeOSTypes</key> <array> <string>BLND</string> </array> <key>CFBundleTypeRole</key> <string>Editor</string> <key>LSIsAppleDefaultForType</key> <true/> </dict> </array> <key>CFBundleExecutable</key> <string>Blender</string> <key>CFBundleGetInfoString</key> <string>2.83.15 2021-05-19, Blender Foundation</string> <key>CFBundleIconFile</key> <string>blender icon.icns</string> <key>CFBundleIdentifier</key> <string>org.blenderfoundation.blender</string> <key>CFBundleInfoDictionaryVersion</key> <string>6.0</string> <key>CFBundleName</key> <string>Blender</string> <key>CFBundlePackageType</key> <string>APPL</string> <key>CFBundleShortVersionString</key> <string>2.83.15</string> <key>CFBundleSignature</key> <string>????</string> <key>CFBundleVersion</key> <string>2.83.15 2021-05-19</string> <key>NSPrincipalClass</key> <string>NSApplication</string> <key>NSHighResolutionCapable</key> <true/> </dict> </plist> ```
Member

As a developer, it might make sense to use that value as current OS. @Sebastián Barschkis (sebbas) would need to confirm this.

std::filesystem (at least partially) std::optional::value(see 9734a78bc8) etc are not available for macOS 10.13, they were added in 10.15 and 10.14 respectively. If this suggestion of leaving CMAKE_OSX_DEPLOYMENT_TARGET to current macOS is implemented, someone on a newer OS version will commit code using std::filesystem and break builds for older OSes. Correct CMAKE_OSX_DEPLOYMENT_TARGET and thus correct -mmacosx-version-min=${CMAKE_OSX_DEPLOYMENT_TARGET}") ensures that such errors are caught at build time on that developer's system.

Also, overriding CMAKE_OSX_DEPLOYMENT_TARGET on the builder is a patchwork and increased workload when the code is fully capable of fixing it.

Ideal fix would be to do something like D10838: WIP attempt to set CMAKE_OSX_SYSROOT before project call: setting CMAKE_OSX_DEPLOYMENT_TARGET, CMAKE_OSX_SYSROOT etc before project call. But less than ideal, fixing it at https://developer.blender.org/diffusion/B/browse/master/build_files/cmake/platform/platform_apple_xcode.cmake$178-185 is also fine by me (fwiw).

> As a developer, it might make sense to use that value as current OS. @Sebastián Barschkis (sebbas) would need to confirm this. `std::filesystem` (at least partially) `std::optional::value`(see 9734a78bc8) etc are not available for macOS 10.13, they were added in 10.15 and 10.14 respectively. If this suggestion of leaving `CMAKE_OSX_DEPLOYMENT_TARGET` to current macOS is implemented, someone on a newer OS version will commit code using `std::filesystem` and break builds for older OSes. Correct `CMAKE_OSX_DEPLOYMENT_TARGET` and thus correct ` -mmacosx-version-min=${CMAKE_OSX_DEPLOYMENT_TARGET}")` ensures that such errors are caught at build time on that developer's system. Also, overriding `CMAKE_OSX_DEPLOYMENT_TARGET` on the builder is a patchwork and increased workload when the code is fully capable of fixing it. Ideal fix would be to do something like [D10838: WIP attempt to set CMAKE_OSX_SYSROOT before project call](https://archive.blender.org/developer/D10838): setting `CMAKE_OSX_DEPLOYMENT_TARGET`, `CMAKE_OSX_SYSROOT` etc before `project` call. But less than ideal, fixing it at https://developer.blender.org/diffusion/B/browse/master/build_files/cmake/platform/platform_apple_xcode.cmake$178-185 is also fine by me (fwiw).
Member

I would prefer to override CMAKE_OSX_DEPLOYMENT_TARGET via new build pipeline that will apply the value across all branches in case this changes again.

Oh for older releases which are still being built on the builder, this sounds good. But best to ask an admin or the LTS manager about that.

> I would prefer to override CMAKE_OSX_DEPLOYMENT_TARGET via new build pipeline that will apply the value across all branches in case this changes again. Oh for older releases which are still being built on the builder, this sounds good. But best to ask an admin or the LTS manager about that.

Yes, I am proposing a change to override cmake option to set the MIN onto the supported version release branch and would only apply when running with buildbot.
We could also ensure the cmake file is correct on all branches instead.

However, still not sure how this would be a problem in 2.83.14 though, as I don't think that file changed there.

Yes, I am proposing a change to override cmake option to set the MIN onto the supported version release branch and would only apply when running with buildbot. We could also ensure the cmake file is correct on all branches instead. However, still not sure how this would be a problem in 2.83.14 though, as I don't think that file changed there.

This issue was referenced by 2e7d3ad7b5

This issue was referenced by 2e7d3ad7b51bbc05cdcbbc3c055f961f3a2c28a8
Member

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Ankit Meel self-assigned this 2021-05-20 18:27:32 +02:00

This issue was referenced by 704f56d68f

This issue was referenced by 704f56d68f3ed83e6350f182fcf9aa45a19ded41

When will 2.83.15, 2.93 Beta & 3.00 Alpha versions available to download with support for macOS 10.13+?

When will 2.83.15, 2.93 Beta & 3.00 Alpha versions available to download with support for macOS 10.13+?
Member

@Oxer-1 2.93, 3.0 arm and intel versions have been updated as of now.
2.83 will be updated in a day. Ping us if it doesn't.

@Oxer-1 2.93, 3.0 arm and intel versions have been updated as of now. 2.83 will be updated in a day. Ping us if it doesn't.
Member

Added subscribers: @BlenderBruno, @lichtwerk

Added subscribers: @BlenderBruno, @lichtwerk

In #88419#1163720, @ankitm wrote:
@Oxer-1 2.93, 3.0 arm and intel versions have been updated as of now.
2.83 will be updated in a day. Ping us if it doesn't.

The 2.83.15 LTS is not updated yet.

> In #88419#1163720, @ankitm wrote: > @Oxer-1 2.93, 3.0 arm and intel versions have been updated as of now. > 2.83 will be updated in a day. Ping us if it doesn't. The 2.83.15 LTS is not updated yet.
Member

In #88419#1165112, @Oxer-1 wrote:

In #88419#1163720, @ankitm wrote:
@Oxer-1 2.93, 3.0 arm and intel versions have been updated as of now.
2.83 will be updated in a day. Ping us if it doesn't.

The 2.83.15 LTS is not updated yet.

The fix is in 2.83.16 #77348 (Blender LTS: Maintenance Task 2.83)

> In #88419#1165112, @Oxer-1 wrote: >> In #88419#1163720, @ankitm wrote: >> @Oxer-1 2.93, 3.0 arm and intel versions have been updated as of now. >> 2.83 will be updated in a day. Ping us if it doesn't. > > The 2.83.15 LTS is not updated yet. The fix is in 2.83.16 #77348 (Blender LTS: Maintenance Task 2.83)

Thanks for the info!!

Thanks for the info!!
Member

Added subscriber: @angadmishra

Added subscriber: @angadmishra
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
FBX
Interest
Freestyle
Interest
Geometry Nodes
Interest
glTF
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Asset System
Module
Core
Module
Development Management
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
9 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#88419
No description provided.