Jump to content

Can't check for content updates with Accordance 14.0.2


Accordance Enthusiast

Recommended Posts

I have the same problem if I use 'Check for Contents Updates' on the menu, but if I use 'Easy Install' on the menu instead, I can successfully access the updates check from there. See if that will work for update checks until this bug can be resolved.

Link to comment
Share on other sites

Perhaps this is windows exclusive. I'm not having this problem on macOS. 

Link to comment
Share on other sites

16 minutes ago, A. Smith said:

Perhaps this is windows exclusive. I'm not having this problem on macOS. 

 

That's a distinct possibility if other Mac users are not experiencing this problem. I often came across such issues on one platform only when working as a technician.

Link to comment
Share on other sites

Since buying accordance there has always been more bugs on Windows than on Mac.

Link to comment
Share on other sites

I don't experience this on my Mac, but I do see it on the Windows machine in my office.  (And I saw it in accordance 14 there, too).  If I remember correctly, clicking the "Easy Install" button and then one that pane/tab appears/resolves clicking "Updates" usually clears it and lets me check for updates.  I'm not currently in my office to double check that. 

Link to comment
Share on other sites

I have the same problem on Mac. Running arm version on Ventura. When I try to open the crash log it says I don't have permission.

 

1934336641_accordancecrash.thumb.png.bd46437595eba31cc302ab1c6e20476e.png

  • Like 1
Link to comment
Share on other sites

Not sure how this works, but here goes. I have this same problem on my Mac. When I go to check Content updates, Accordance crashes.

Also, I have had a collection of Workspaces 1,2,3,4,5, and in the previous version, when I clicked on Windows, I could see each of the workspaces and select. New version has somehow named the workspaces with names that mean nothing to me, so getting to where I want to go is becoming very cumbersome. Not a fan of ACCORDANCE 14.

 

Link to comment
Share on other sites

I have the same issue on MacOSX. 

The crash log reports: Access violation from /Applications/Accordance.app/Contents/MacOS/acord.

 

I upload the crash log to help the programmer quickly identify the root cause.

Accordance 2022-12-09 at 16.30.27.crash.txt

  • Like 1
Link to comment
Share on other sites

@KevinPurcell I had this same "don't have permission" error for crash logs.  I was able to access them by navigating directly to them:

 

In Finder, hold down the option key, then go to the Go menu and choose Library.  From there the path to find them is:

 

Library>Logs>Diagnostic Reports

 

the log file names will start with "Accordance"

 

Note:  I'm on Monterey, not Ventura, so it's possible there might be a bit of variation in how to find them. 

 

Link to comment
Share on other sites

I'm having the same issue on a Mac but it's not exclusive to Accordance 14. It's happening in v13 too. Maybe something changed on the server side that's affecting this? Idk. Crash log below. 

 

 

 

Accordance Crash Log
12/9/22, 11:43:25 AM

Accordance Aleph 13.3.4 (13.3.4)
CPU: aarch64
MacOS 12.6.1 "Monterey"

Message: Access violation
Address:   $0000000104235688

Backtrace:
0   acord                               0x0000000104235688 acord + 1775240
1   acord                               0x00000001041e0db4 acord + 1428916
2   acord                               0x00000001041e0c5c acord + 1428572
3   acord                               0x00000001041dfbc0 acord + 1424320
4   acord                               0x00000001041e2300 acord + 1434368
5   acord                               0x00000001041d361c acord + 1373724
6   acord                               0x00000001041d3d24 acord + 1375524
7   CoreFoundation                      0x00000001a2f3dd8c _signalEventSync + 216
8   CoreFoundation                      0x9c7d8001a2f91b48 _cfstream_shared_signalEventSync + 11276309779493945736
9   CoreFoundation                      0x25590001a2f10f94 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 2691182252330582044
10  CoreFoundation                      0xb43a8001a2f10ee0 __CFRunLoopDoSource0 + 12986833212964602064
11  CoreFoundation                      0xf1488001a2f10c44 __CFRunLoopDoSources0 + 17386287098952155504
12  CoreFoundation                      0x5d008001a2f0f560 __CFRunLoopRun + 6701496983015654204
13  CoreFoundation                      0x46540001a2f0ea84 CFRunLoopRunSpecific + 5067675480698651224
14  HIToolbox                           0x8b1f8001abb52338 RunCurrentEventLoopInMode + 10024872033038369060
15  HIToolbox                           0x7a5f0001abb520b4 ReceiveNextEventCommon + 8817766595414721076
16  HIToolbox                           0x3d2c8001abb51e68 _BlockUntilNextEventMatchingListInModeWithFilter + 4408038872777228360

Binaries:
0x0000000004084000 /Applications/Accordance Aleph.app/Contents/MacOS/acord
0x000000010528c000 /Applications/Accordance Aleph.app/Contents/Frameworks/SSZipArchive.framework/Versions/A/SSZipArchive
0x000000010553c000 /Applications/Accordance Aleph.app/Contents/Frameworks/Sparkle.framework/Versions/A/Sparkle
0x0000000105ff4000 /Applications/Accordance Aleph.app/Contents/Frameworks/ObjectiveDropboxOfficial.framework/Versions/A/ObjectiveDropboxOfficial
 

Link to comment
Share on other sites

Both 14.0.2 and 13.3.4 crash when doing content update!

 

Mac Monterey

 

Bob

Edited by rcdeacon
Link to comment
Share on other sites

49 minutes ago, JonathanHuber said:

I'm having the same issue on a Mac but it's not exclusive to Accordance 14. It's happening in v13 too. Maybe something changed on the server side that's affecting this? Idk. Crash log below. 


 

I think you may be right: I've been able to update content just fine in Accordance 14 previously, but after your post, I tried to do so again as a test, and it crashes for me, too.

 

And, as @KevinPurcell reported earlier, when I tried to access the crash log from the dialog/error box that popped up in Accordance, I was told I didn't have permission to access it.  I was, however, able to navigate to it as I describe above, so it is attached below.

 

Accordance 2022-12-10 at 09.20.34.crash.txt

Link to comment
Share on other sites

Im having the same issue on ios where it just crashes the app when i check for updates on both my phone and pad.  Easy install works fine so im guessing its a bit more widespread. 
 

my mbp is still on 13 and i havent tried syncing for many moons. 

Edited by ukfraser
Link to comment
Share on other sites

4 hours ago, ukfraser said:

Im having the same issue on ios where it just crashes the app when i check for updates on both my phone and pad.  Easy install works fine so im guessing its a bit more widespread. 
 

my mbp is still on 13 and i havent tried syncing for many moons. 

 

Hmm. I did update on my iPhone Accordance 3.3.1 last week or early this week and had no issues, but now it crashes. I have avoided synching with my MBP due the process corrupting my iOS setup. I await updated iOS Accordance and a stable Accordance 14 for Mac OS.

Link to comment
Share on other sites

Same Problem, using Mac Book Pro, Ventutre and Accordance 14.02

Link to comment
Share on other sites

It works on my iPhone, so it seems iOS is fixed. Good news and a step forward! Thanks

 

Roman

Link to comment
Share on other sites

+1 on this same issue on my Windows. 

Link to comment
Share on other sites

  • 2 weeks later...

Try clicking the gear at the top right then click "refresh list" that worked for me.

  • Like 2
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...