Simply updating won't work, correct?
Bah, it doesn't seem to work, first time I downloaded it, simply overwriting the old file, logged onto relevant characters and /wl collect, /quit, upload, it goes through the upload sequence, then I check my Wowhead account, but none of my characters have appeared other than the shaman and mage which I've already set up manually, and they're out of dateThen I actually deleted the old app, and did the above, same results
Can you paste the log from your upload attempt? You should be able to see it with the little display arrow on the client.
I see there's an update to the update already!
Awesome, can't wait to get home from work and try it out. Heard great things about the tracker, especially when one goes for Loremaster. Loremaster Rockne here I come!I'll post if everything goes well. Thanks guys!
Yay! Thanks! I just downloaded this about 1 day ago, and it wasn't working, but after this last update, everything is dandy!LOVE having access to my recipes, etc. offline!
It's still not uploading for me:"2010.02.17 02:17:01 PM: Checking for supported realms…2010.02.17 02:17:01 PM: Found valid realm: us.logon.worldofwarcraft.com"I've clean installed it twice. It immediately asks to be updated after install to wowhead-client 1.2.1 which seems to work.It also appears to be collecting data properly with /wl collect.
Oh, uhm... in that last upload (the one I just did) it worked.... Hmm.... could have been because I had actually looted things and killed things...*edit* changed update to upload
Thank you, Wowhead, for showing the same devotion to Mac users that Blizzard itself does. Believe me, it's honestly appreciated.(I just wish a few more third parties—and in-game players—did too.)
Thanks! The new version gets past the framework problem, but on starting up I see:2010.02.25 01:37:10 PM: Buffer length should be 1, instead it is 1422010.02.25 01:37:10 PM: Authentication failed.2010.02.25 01:37:10 PM: Checking for Updates…2010.02.25 01:37:10 PM: Looks like you're up to date!I've verified the username and password, restarted and tried from a clean system, similar results. I see the same result if I use bogus login information.
Thanks. The first time I ran it it authenticated, reported "Using account <name>" and looked like it started to upload, then crashed with a bus error:Process: wowhead-client Path: /Applications/wowhead-client.app/Contents/MacOS/wowhead-clientIdentifier: com.flozzle.wowhead-clientVersion: ? (1.2.1)Code Type: X86 (Native)Parent Process: launchd Interval Since Last Report: 17255967 secCrashes Since Last Report: 5Per-App Interval Since Last Report: 237014 secPer-App Crashes Since Last Report: 2Date/Time: 2010-03-01 11:04:36.468 -0800OS Version: Mac OS X 10.5.8 (9L30)Report Version: 6Anonymous UUID: 35E7419A-FBF0-49D9-B970-79B312194EB1Exception Type: EXC_BAD_ACCESS (SIGBUS)Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000Crashed Thread: 0Thread 0 Crashed:0 com.apple.CoreFoundation 0x91f9de58 CFReadStreamRead + 401 com.flozzle.wowhead-client 0x000066d9 - + 552 com.apple.CoreFoundation 0x91f9ab1b _signalEventSync + 913 com.apple.CoreFoundation 0x91f9abbe _cfstream_solo_signalEventSync + 1264 com.apple.CoreFoundation 0x91f9d057 CFReadStreamSignalEvent + 395 com.apple.CFNetwork 0x91505e00 HTTPReadStream::streamEvent(unsigned long) + 686 com.apple.CoreFoundation 0x91f9ab1b _signalEventSync + 917 com.apple.CoreFoundation 0x91f9b492 _cfstream_shared_signalEventSync + 1468 com.apple.CoreFoundation 0x91f893c5 CFRunLoopRunSpecific + 31419 com.apple.CoreFoundation 0x91f89aa8 CFRunLoopRunInMode + 8810 com.apple.HIToolbox 0x95b262ac RunCurrentEventLoopInMode + 28311 com.apple.HIToolbox 0x95b260c5 ReceiveNextEventCommon + 37412 com.apple.HIToolbox 0x95b25f39 BlockUntilNextEventMatchingListInMode + 10613 com.apple.AppKit 0x94c486d5 _DPSNextEvent + 65714 com.apple.AppKit 0x94c47f88 - + 12815 com.apple.AppKit 0x94c40f9f - + 79516 com.apple.AppKit 0x94c0e1d8 NSApplicationMain + 57417 com.flozzle.wowhead-client 0x0000258b _start + 20918 com.flozzle.wowhead-client 0x000024b9 start + 41If I restart it and run it again it finds my account but doesn't upload anything ("Nothing to upload to the server"). However, if I start wow, do a "/wl collect", and exit, then click "upload" in the still running Wowhead Client, it succeeds:Using account <my account>2010.03.01 11:11:07 AM: Validating data…2010.03.01 11:11:07 AM: Initiating upload…2010.03.01 11:11:11 AM: Cleaning up…2010.03.01 11:11:11 AM: Upload successful. You can upload again after 1 minute.I'm not sure if it is related to this upload, but it appears my character's profile is currently broken, the browser console is reporting:Error: g_quest_catorder is not definedSource File: http://static.wowhead.com/js/Profiler.js?690Just to give y'all more relevant information, I did upload data from a non-macos client in late February. All the details here are from March 1st.Thanks again!
Very similar to above:2010.04.07 06:59:48 PM: Checking for supported realms…2010.04.07 06:59:48 PM: Found valid realm: us.logon.worldofwarcraft.com2010.04.07 06:59:55 PM: Checking for supported realms…2010.04.07 06:59:55 PM: Found valid realm: us.logon.worldofwarcraft.comWhen I switch over to my Admin account the program runs fine...Is it possible that the program is trying to write into the data area hidden "under" the Application...that is a no-no on secure systems (unix is trying to be as secure as possible). It is an old Microsoft bad-habit to write into application space and hence viruses have free play :-)The Warcraft application is only writeable by admin, however, I have had to add the users to the data-only sections of the warcraft (and W T F) folders (bit of a pain, but not your fault).
Hmm...well running it as an admin should be a good workaround. For any additional issues I'm going to have to track down the volunteer who built us the damn thing. :)
I reliably get the SIGBUS error as well. This is with wowhead-client 1.2.1.This error occurs only when there's actually data to upload. The upload does seem to succeed (in that I can see my characters' profiles), but I'm not certain about all the other collected data.I have 3 WoW accounts—perhaps that's an issue? The log window seems to indicate that it goes through each one OK.Here's the (partial) stack trace from the error reporter—can't post the full because it exceeds the post limit:Process: wowhead-client Path: /Applications/Games/World Of Warcraft/wowhead-client.app/Contents/MacOS/wowhead-clientIdentifier: com.flozzle.wowhead-clientVersion: ? (1.2.1)Code Type: X86 (Native)Parent Process: launchd Date/Time: 2010-04-20 21:57:23.818 -0500OS Version: Mac OS X 10.6.3 (10D573)Report Version: 6Interval Since Last Report: 488347 secCrashes Since Last Report: 3Per-App Interval Since Last Report: 6481 secPer-App Crashes Since Last Report: 2Anonymous UUID: E8FF6C48-4171-4915-9CAF-D73B8359E0B5Exception Type: EXC_BAD_ACCESS (SIGBUS)Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000Crashed Thread: 0 Dispatch queue: com.apple.main-threadThread 0 Crashed: Dispatch queue: com.apple.main-thread0 com.apple.CoreFoundation 0x957d8a50 CFReadStreamRead + 961 com.flozzle.wowhead-client 0x000066d9 - + 552 com.apple.CoreFoundation 0x95858dd3 _signalEventSync + 993 com.apple.CoreFoundation 0x958597be _cfstream_solo_signalEventSync + 1264 com.apple.CoreFoundation 0x95858a88 _CFStreamSignalEvent + 7925 com.apple.CoreFoundation 0x95859707 CFReadStreamSignalEvent + 396 com.apple.CFNetwork 0x95d41a7f HTTPReadStream::streamEvent(unsigned long) + 1697 com.apple.CoreFoundation 0x95858dd3 _signalEventSync + 998 com.apple.CoreFoundation 0x95858d58 _cfstream_shared_signalEventSync + 6649 com.apple.CoreFoundation 0x957cf15b __CFRunLoopDoSources0 + 156310 com.apple.CoreFoundation 0x957ccc1f __CFRunLoopRun + 107111 com.apple.CoreFoundation 0x957cc0f4 CFRunLoopRunSpecific + 45212 com.apple.CoreFoundation 0x957cbf21 CFRunLoopRunInMode + 9713 com.apple.HIToolbox 0x97a8f0fc RunCurrentEventLoopInMode + 39214 com.apple.HIToolbox 0x97a8eeb1 ReceiveNextEventCommon + 35415 com.apple.HIToolbox 0x97a8ed36 BlockUntilNextEventMatchingListInMode + 8116 com.apple.AppKit 0x98bb6135 _DPSNextEvent + 84717 com.apple.AppKit 0x98bb5976 - + 15618 com.apple.AppKit 0x98b77bef - + 82119 com.apple.AppKit 0x98b6fc85 NSApplicationMain + 57420 com.flozzle.wowhead-client 0x0000258b _start + 20921 com.flozzle.wowhead-client 0x000024b9 start + 41Thread 1: Dispatch queue: com.apple.libdispatch-manager0 libSystem.B.dylib 0x97da6b42 kevent + 101 libSystem.B.dylib 0x97da725c _dispatch_mgr_invoke + 2152 libSystem.B.dylib 0x97da6719 _dispatch_queue_invoke + 1633 libSystem.B.dylib 0x97da64be _dispatch_worker_thread2 + 2404 libSystem.B.dylib 0x97da5f41 _pthread_wqthread + 3905 libSystem.B.dylib 0x97da5d86 start_wqthread + 30Thread 2:0 libSystem.B.dylib 0x97d802fa mach_msg_trap + 101 libSystem.B.dylib 0x97d80a67 mach_msg + 682 com.apple.CoreFoundation 0x957cd00f __CFRunLoopRun + 20793 com.apple.CoreFoundation 0x957cc0f4 CFRunLoopRunSpecific + 4524 com.apple.CoreFoundation 0x957cbf21 CFRunLoopRunInMode + 975 com.apple.Foundation 0x92edf434 + + 3296 com.apple.Foundation 0x92ea68dc - + 457 com.apple.Foundation 0x92ea688c __NSThread__main__ + 14998 libSystem.B.dylib 0x97dada19 _pthread_start + 3459 libSystem.B.dylib 0x97dad89e thread_start + 34Thread 3:0 libSystem.B.dylib 0x97d9f286 select$DARWIN_EXTSN + 101 com.apple.CoreFoundation 0x9580c82d __CFSocketManager + 10852 libSystem.B.dylib 0x97dada19 _pthread_start + 3453 libSystem.B.dylib 0x97dad89e thread_start + 34Thread 4:0 libSystem.B.dylib 0x97da5bd2 __workq_kernreturn + 101 libSystem.B.dylib 0x97da6168 _pthread_wqthread + 9412 libSystem.B.dylib 0x97da5d86 start_wqthread + 30Thread 0 crashed with X86 Thread State (32-bit): eax: 0xa07458cc ebx: 0x957d89fe ecx: 0x0013b500 edx: 0x00000023 edi: 0x254bed60 esi: 0x00000000 ebp: 0xbfffe6a8 esp: 0xbfffe640 ss: 0x0000001f efl: 0x00010283 eip: 0x957d8a50 cs: 0x00000017 ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037 cr2: 0x00000000Good luck to Rudy in figuring this out! ^.^
Well, back in February when I first downloaded the looter everything was working fine. Then, a couple months ago, every time I tried to upload data the program freezes up and just sits there. No "Checking for supported realms…"No "Found valid realm: us.logon.worldofwarcraft.com"No nothing. It just sits there frozen. Anyone else experiencing this problem or know what I can do?Thanks!
Is this still happening? Can you expand the logbox at the bottom and copy/paste the contents here so I can see the logs?