Daz Install Manager won't open on MacOS Mojave

bevdog896_d08d9c913a

Hi there! Just upgraded my mac to macos mojave. Daz studio is working fine but when I tried to open daz install manager a message appeared saying 'the application cannot be opened." Any ideas? 

Wish I'd not been so hasty in upgrading my macos now ????

Thanks

Edit: Thought it might be a security thing as Mojave is set to only open apps from recognised developers (daz is, but the install manager isn’t for some reason). Enable that in settings, still wouldn’t open.

I then uninstalled and reinstalled, still won’t work. I’m guessing I may have to wait for daz to update install manager again and then redownload it maybe? 

I guess the lesson is don’t update your operating system a day after it’s available lol. 

ee8f613e80

Daz and the installer will not install under MOjave for me as well. I hope they fix it quick. 

Platnumk

Open Terminal and enter the following line

sudo spctl --master-disable

then enter you password

You should now have the option under your security options to allow from anywhere

when you are done installing then enter this line into the terminal to put gatekeeper back to its default state

sudo spctl --master-enable

then enter yourt password

Hope this helps

mikki_880ac1f9

Same problem here, crashes without even trying to starup! Platnumk, the above did not work for me unfortunatley, but thank you. I also have to admit I am not a pro in using the terminal by any means. The crash report is per usual not redable by be and my minor knowledge of crashed apps in Apple and its following code, but I will post it if someone request it. I'm not sure what the problem may be, but will wait for a few more days to see if something comes up on this issue. 

bevdog896_d08d9c913a

Platnumk said:

Open Terminal and enter the following line

sudo spctl --master-disable

then enter you password

You should now have the option under your security options to allow from anywhere

when you are done installing then enter this line into the terminal to put gatekeeper back to its default state

sudo spctl --master-enable

then enter yourt password

Hope this helps

Thanks for the info. I managed to get past the security thing by sorting it out in system prefs - privacy and security. My issue is basically DAZIM just crashes on launch every time. Studio is fine though, it's really odd. Must be an incompatibility with mojave at the moment i guess. I don't mind installing products manually but the install manager is useful when daz itself has an update. Hope there's a patch for the IM soon :) 

bevdog896_d08d9c913a

mikki_880ac1f9 said:

Same problem here, crashes without even trying to starup! Platnumk, the above did not work for me unfortunatley, but thank you. I also have to admit I am not a pro in using the terminal by any means. The crash report is per usual not redable by be and my minor knowledge of crashed apps in Apple and its following code, but I will post it if someone request it. I'm not sure what the problem may be, but will wait for a few more days to see if something comes up on this issue. 

I'm hoping for the same thing. Hopefully daz release an updated version of the install manager soon :) 

Platnumk

Not sure if you have tried this,  but have you tried downloading the 64bit version of DIM, The reason I ask this is that as from MacOS Mojave 32bit apps are no longer supprted

bevdog896_d08d9c913a

Not sure if you have tried this,  but have you tried downloading the 64bit version of DIM, The reason I ask this is that as from MacOS Mojave 32bit apps are no longer supprted

Yea been using the 64bit version since it was released :) 

 

bevdog896_d08d9c913a

Just a thought as well. For anyone else having this issue, can always use DAZ connect (from within the studio itself) as an alternative to DAZIM and manual installation in the meantime. I totally forgot that was a thing lol

Rob_272036

Same problem here after the Mojave update

Using the 64 bit version of DAZ install manager

bytescapes

Platnumk said:

Not sure if you have tried this,  but have you tried downloading the 64bit version of DIM, The reason I ask this is that as from MacOS Mojave 32bit apps are no longer supprted

According to the things I've read, Mojave still officially supports 32-bit apps, but it will be the last release of MacOS to do so. Whatever comes after Mojave will be 64-bit only.

There have been some reports of issues with certain 32-bit apps, and it's definitely worth migrating to the 64-bit version of DAZ Install Manager (or anything else that comes in both 32-bit and 64-bit versions).

ACFan

I did a long writeup on this in the MAC FAQ as a response - it might help with understanding where we're sitting on the DIM issue. https://www.daz3d.com/forums/discussion/16599/the-mac-faq#latest

bevdog896_d08d9c913a

ACFan said:

I did a long writeup on this in the MAC FAQ as a response - it might help with understanding where we're sitting on the DIM issue. https://www.daz3d.com/forums/discussion/16599/the-mac-faq#latest

 

Thanks :) At the moment I’m just relying on the daz connect feature

Iamcaobin

I've fresh installed system with macOS Mojave but DIM crash.. I really hope the update of DIM is coming soon????????~

lutherdan_f779727b4f

I was using the Beta of Mojave and posted crash reports and gave screenshots. Basicly told "it's Beta, leave us alone". Don't guess the team was very interested in Mac users. 

Richard Haseltine

https://www.daz3d.com/forums/discussion/comment/3996201/#Comment_3996201

Iamcaobin

Iamcaobin said:

I've fresh installed system with macOS Mojave but DIM crash.. I really hope the update of DIM is coming soon????????~

this is the version of DIM with crash DAZ3DIM_1.1.0.100_Mac64

MacSavers

Same here. Here's the part of the report that I sent to Apple. I can't post the whole thing. The forum says it's 38,439 characters too long. So I've included a PDF attachment.

Process:               DAZ3DIM [14437]
Path:                  /Applications/DAZ 3D/*/DAZ3DIM.app/Contents/MacOS/DAZ3DIM
Identifier:            com.DAZ.DAZ3DIM
Version:               1.0 (1.1.0.100)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           DAZ3DIM [14437]
User ID:               502

Date/Time:             2018-10-01 12:43:13.771 -0500
OS Version:            Mac OS X 10.14 (18A391)
Report Version:        12
Anonymous UUID:        BB2130FA-0A3B-CD49-1C61-8DA451E3FEB5

Time Awake Since Boot: 310000 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
abort() called

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib            0x00007fff5f612b86 __pthread_kill + 10
1   libsystem_pthread.dylib           0x00007fff5f6c8c50 pthread_kill + 285
2   libsystem_c.dylib                 0x00007fff5f57c1c9 abort + 127
3   QtCore                            0x0000000100b95255 qt_message_output(QtMsgType, char const*) + 149
4   QtCore                            0x0000000100b9544e qt_message(QtMsgType, char const*, __va_list_tag*) + 446
5   QtCore                            0x0000000100b9568d qFatal(char const*, ...) + 141
6   QtCore                            0x0000000100b956be qt_assert_x(char const*, char const*, char const*, int) + 30
7   com.DAZ.DAZ3DIM                   0x000000010000dab9 __static_initialization_and_destruction_0(int, int) + 12009
8   dyld                              0x0000000101dd0cc8 ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) + 518
9   dyld                              0x0000000101dd0ec6 ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) + 40
10  dyld                              0x0000000101dcc0da ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, char const*, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 358
11  dyld                              0x0000000101dcb254 ImageLoader::processInitializers(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 134
12  dyld                              0x0000000101dcb2e8 ImageLoader::runInitializers(ImageLoader::LinkContext const&, ImageLoader::InitializerTimingList&) + 74
13  dyld                              0x0000000101dba774 dyld::initializeMainExecutable() + 199
14  dyld                              0x0000000101dbf78f dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, unsigned long*) + 6237
15  dyld                              0x0000000101db94f6 dyldbootstrap::start(macho_header const*, int, char const**, long, macho_header const*, unsigned long*) + 1154
16  dyld                              0x0000000101db9036 _dyld_start + 54

Thread 1:: QProcessManager
0   libsystem_kernel.dylib            0x00007fff5f613e82 __select + 10
1   QtCore                            0x0000000100c6df7e QProcessManager::run() + 214
2   QtCore                            0x0000000100b9f5ca QThreadPrivate::start(void*) + 464
3   libsystem_pthread.dylib           0x00007fff5f6c633d _pthread_body + 126
4   libsystem_pthread.dylib           0x00007fff5f6c92a7 _pthread_start + 70
5   libsystem_pthread.dylib           0x00007fff5f6c5425 thread_start + 13

Thread 2:
0   libsystem_pthread.dylib           0x00007fff5f6c5408 start_wqthread + 0
1   ???                               0x0000000054485244 0 + 1414025796

Thread 3:
0   libsystem_pthread.dylib           0x00007fff5f6c5408 start_wqthread + 0
1   ???                               0x0000000054485244 0 + 1414025796

Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0x0000000000000000  rbx: 0x0000000101e6e5c0  rcx: 0x00007ffeefbfc3f8  rdx: 0x0000000000000000
  rdi: 0x0000000000000307  rsi: 0x0000000000000006  rbp: 0x00007ffeefbfc430  rsp: 0x00007ffeefbfc3f8
   r8: 0x00000000000130a8   r9: 0x0000000000000000  r10: 0x0000000000000000  r11: 0x0000000000000206
  r12: 0x0000000000000307  r13: 0x00007ffeefbfc760  r14: 0x0000000000000006  r15: 0x000000000000002d
  rip: 0x00007fff5f612b86  rfl: 0x0000000000000206  cr2: 0x00007fff912e4188
  
Logical CPU:     0
Error Code:      0x02000148
Trap Number:     133

mrjaded

I use the 64bit installer and when it stopped working I tried the 32bit one on the off chance that it might work. It didn't. Neither will work under Mojave.

This is very boring. How long will we have to wait for an update?

Iamcaobin

Daz developer respond me as:

Please install using Daz Connect while we resolve the crashing with Install Manager on Mojave. I apologize for the inconvenience.

So.. somebody tell me how to using Daz Connect instead DIM please.. ?

rsharp_3144816

I had an older copy of DIM on my Mac (DAZ3DIM_1.1.0.72_Mac32).  I know that another thread stated that older downloads are not made available (a mistake, IMO).

Anyone, when I first ran that particular version, it would connect, then immediately want to install the newer version.  I got strange errors and ultimately the new version would launch, but do nothing.  I kept un-installing and tried the 1.1.0.72 again.  At one point, it didn't prompt me to install the new version and all was then well.

So if you have access to an older DIM, give that a try.

Richard Haseltine

Older versions of DIM should not connect to thes tore at all, they shoudl just trigger an update request - that's because both stroe and DIM need to be working to the same protocols. What you can do is manually download the zip (not "Download and Install"), place that in the Downloads folder, and launch the older version of DIM in Work Offline mode to install - though even there I should think there's a risk of a change to teh .dsx manifest files causing issues.

Iamcaobin

Richard Haseltine said:

Older versions of DIM should not connect to thes tore at all, they shoudl just trigger an update request - that's because both stroe and DIM need to be working to the same protocols. What you can do is manually download the zip (not "Download and Install"), place that in the Downloads folder, and launch the older version of DIM in Work Offline mode to install - though even there I should think there's a risk of a change to teh .dsx manifest files causing issues.

Have you meant even the older versions of DIM wouldn't crash in Mojave, it will not work fine online.. right?

Iamcaobin

It seems there is a long time need to wait for the Install Manager updated on Mojave, so.. does Daz Connect is using as same as Install Manager.. ?

Chohole

Iamcaobin said:

It seems there is a long time need to wait for the Install Manager updated on Mojave, so.. does Daz Connect is using as same as Install Manager.. ?

what was said 

DAZ_Rawb said:

I have spoken with the development team and they have found the problem and are developing a solution.

 

The fix will have to be tested both internally and through a beta test team to make sure that it not only fixes it on Mojave but doesn't break it on other platforms. If the testing reveals other problems then the release will be delayed, so I can't give an estimate of when this will release but I just wanted to make it clear that progress is being made on this right now.

 

rsharp_3144816

Richard Haseltine said:

Older versions of DIM should not connect to thes tore at all, they shoudl just trigger an update request - that's because both stroe and DIM need to be working to the same protocols. What you can do is manually download the zip (not "Download and Install"), place that in the Downloads folder, and launch the older version of DIM in Work Offline mode to install - though even there I should think there's a risk of a change to teh .dsx manifest files causing issues.

Well thankfully it does.  I just purchased another asset this morning.  Showed up a-ok in the older DIM.  Why wouldn't it work? It would really only not work if the protocols on how files are received would change.  Why would users always be forced to the latest version?  Unless Daz is going to guarantee compatibility with all OS versions, it's in their best interest to provide a reasonable range of prior versions.

Richard Haseltine

Because protocols might well chnage - the system is designed to be modifable - and if you look at the change log you will see suggestions that changes are being made. Having the system always insist on using the latest version ensures that everything is in sync.

Iamcaobin

rsharp said:

Richard Haseltine said:

Older versions of DIM should not connect to thes tore at all, they shoudl just trigger an update request - that's because both stroe and DIM need to be working to the same protocols. What you can do is manually download the zip (not "Download and Install"), place that in the Downloads folder, and launch the older version of DIM in Work Offline mode to install - though even there I should think there's a risk of a change to teh .dsx manifest files causing issues.

Well thankfully it does.  I just purchased another asset this morning.  Showed up a-ok in the older DIM.  Why wouldn't it work? It would really only not work if the protocols on how files are received would change.  Why would users always be forced to the latest version?  Unless Daz is going to guarantee compatibility with all OS versions, it's in their best interest to provide a reasonable range of prior versions.

Have you meant.. the older version of DIM works without any problem on macOS Mojave right? If so I wonder do you have the copy of this version?

Richard Haseltine

Iamcaobin said:

rsharp said:

Richard Haseltine said:

Older versions of DIM should not connect to thes tore at all, they shoudl just trigger an update request - that's because both stroe and DIM need to be working to the same protocols. What you can do is manually download the zip (not "Download and Install"), place that in the Downloads folder, and launch the older version of DIM in Work Offline mode to install - though even there I should think there's a risk of a change to teh .dsx manifest files causing issues.

Well thankfully it does.  I just purchased another asset this morning.  Showed up a-ok in the older DIM.  Why wouldn't it work? It would really only not work if the protocols on how files are received would change.  Why would users always be forced to the latest version?  Unless Daz is going to guarantee compatibility with all OS versions, it's in their best interest to provide a reasonable range of prior versions.

Have you meant.. the older version of DIM works without any problem on macOS Mojave right? If so I wonder do you have the copy of this version?

Regardless, I'm afraid. no one else may give you a copy if you don't have one

Iamcaobin

Richard Haseltine said:

Iamcaobin said:

rsharp said:

Richard Haseltine said:

Older versions of DIM should not connect to thes tore at all, they shoudl just trigger an update request - that's because both stroe and DIM need to be working to the same protocols. What you can do is manually download the zip (not "Download and Install"), place that in the Downloads folder, and launch the older version of DIM in Work Offline mode to install - though even there I should think there's a risk of a change to teh .dsx manifest files causing issues.

Well thankfully it does.  I just purchased another asset this morning.  Showed up a-ok in the older DIM.  Why wouldn't it work? It would really only not work if the protocols on how files are received would change.  Why would users always be forced to the latest version?  Unless Daz is going to guarantee compatibility with all OS versions, it's in their best interest to provide a reasonable range of prior versions.

Have you meant.. the older version of DIM works without any problem on macOS Mojave right? If so I wonder do you have the copy of this version?

Regardless, I'm afraid. no one else may give you a copy if you don't have one

Please. Thanks you so much!

Leana

Iamcaobin said:

Richard Haseltine said:

Iamcaobin said:

rsharp said:

Richard Haseltine said:

Older versions of DIM should not connect to thes tore at all, they shoudl just trigger an update request - that's because both stroe and DIM need to be working to the same protocols. What you can do is manually download the zip (not "Download and Install"), place that in the Downloads folder, and launch the older version of DIM in Work Offline mode to install - though even there I should think there's a risk of a change to teh .dsx manifest files causing issues.

Well thankfully it does.  I just purchased another asset this morning.  Showed up a-ok in the older DIM.  Why wouldn't it work? It would really only not work if the protocols on how files are received would change.  Why would users always be forced to the latest version?  Unless Daz is going to guarantee compatibility with all OS versions, it's in their best interest to provide a reasonable range of prior versions.

Have you meant.. the older version of DIM works without any problem on macOS Mojave right? If so I wonder do you have the copy of this version?

Regardless, I'm afraid. no one else may give you a copy if you don't have one

Please. Thanks you so much!

No one is allowed to give you a copy. If you don't have a backup of it yourself then you'll have to wait until the new version with the fix is released.