This site makes extensive use of JavaScript.
Please enable JavaScript in your browser.
Classic Theme
Thottbot Theme
Mac OS X Client Bugs
Post Reply
Return to board index
Post by
1355096
This post was from a user who has deleted their account.
Post by
SnowyRow
Thank you a thousand times, czeano! With your file I was finally able to reactivate my looter! That is very much appreciated!
Post by
Ooyeah
Using terminal works a dream. Wowhead needs to update the instructions with that information.
Post by
amjbrown
Fantastic - thank you!
Post by
Guppeth
The terminal command worked for me after I failed to get the Textedit method to work. I figured out WHY the Textedit method failed afterwards.
Textedit had saved the file as realmlist.wtf
.txt
OS X hides the .txt extension by default, so I didn't realise it was wrong. The terminal command created what appeared to be a duplicate file, and that's when I figured it out.
So the original instructions are correct, but don't account for Textedit and OS X's little idiosyncrasies.
Post by
1375768
This post was from a user who has deleted their account.
Post by
alphabit
I just had the "unsupported realm" error and after googling was able to fix it.
Using terminal helps a lot, here is a guide on the commands
1. Browse to your WoW main directory,
cd <path here>/World\ of\ Warcraft/
(using the tab key to autocomplete folder names helps by the way!
2. Browse to the following subfolder,
cd Data/enUS/
3. Create an empty realmlist file,
touch realmlist.wtf
4. Open the realmlist file for editing,
nano realmlist.wtf
(this will open the file in terminal's nano text editor)
5. Write the following into nano,
set realmlist us.logon.worldofwarcraft.com
6. Save the file changes with control+O, this will display the message 'File Name to Write: realmlist.wtf' so just press enter
7. Press control+X to exit (if you like doing things the clean way)
And you're done! Restart the Wowhead Client and Upload!
Post by
nechin
...
Turns out textedit was saving the document as a "text document", even though I set it to plain text.
The echo method just makes it a "file".
...
You have discovered a problem I was having too, the default settings add a .txt on the end and then hide it from you!
No need to use terminal commands though, just
untick
the option "If no extension is provided, use ".txt."."
Post by
Jujuzita
It's not working for me. This WoWClient is really buggy. I do want my followers here but I cannot do it...
Post by
maccormaic
I'm having some trouble of a different sort. I have the configuration down, and I can execute the client successfully. It runs fine until it attempts to connect to the remote host. It then crashes with the following:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
There's more, but I thought I'd wait to see if anyone else has seen this. Additional information:
Process: wowhead-client
Path: /Applications/Wowhead Client.app/Contents/MacOS/wowhead-client
Identifier: com.flozzle.wowhead-client
Version: 1.2.2
Code Type: X86 (Native)
Parent Process: ?
Responsible: wowhead-client
User ID: 501
Date/Time: 2015-07-01 20:02:58.415 -0700
OS Version: Mac OS X 10.10.3 (14D136)
Any thoughts?
Post by
42912
This post was from a user who has deleted their account.
Post by
jimbobaus
If you do the textedit fix above.. make sure when u put the file in your WOW folder.. u right click on it delete the.txt extension in the GET INFO and it will ask you.. use txt or use wtf.. chose wtf and boom you can upload your data :)
Post by
Hielke
After fixing the real file I got the client working however the text is black and the back ground is near black. This makes reading the buttons quite hard. I made a screenshot but can't upload it here so if you need the screenshot just ask and i'll email it to you.
Post by
Loisse
5 days ago, my Mac OS X client stopped authenticating my account correctly. I did not change any Wowhead-associated passwords, or the account information in the client prior to it ceasing to function.
When I launch the client, I get the messages:
2015.09.06 06:29:50 PM: Authentication succeeded.
2015.09.06 06:29:50 PM: Checking for Wowhead Looter addon updates…
2015.09.06 06:29:51 PM: Looks like you're up-to-date!
and then when I click the Upload button:
2015.09.06 06:30:44 PM: Authentication failed.
and when I go into Account Setup and re-enter my login information:
2015.09.06 06:33:21 PM: Invalid Wowhead credentials
I have changed my password on the Wowhead site (twice), and that doesn't make a difference.
I have tried using my email address (as per original setup), my Wowhead login name, and my ZAM login name, and none of them work.
I'd like to continue to upload data - any ideas?
Post by
Loisse
Solved by logging out, and then using the 'Forgot password' link on Wowhead (
not
ZAM) to reset my password. Had to restart the Wowhead client several times after that, but it finally decided to upload again. Whew!
Post by
Ludovico
Well, today my mac Wowhead-client bit the dust:
Process: wowhead-client
Path: /Applications/wowhead-client.app/Contents/MacOS/wowhead-client
Identifier: com.flozzle.wowhead-client
Version: 1.2.1
Code Type: X86 (Native)
Parent Process: ?
Responsible: wowhead-client
User ID: 504
Date/Time: 2016-02-15 16:38:00.925 -0500
OS Version: Mac OS X 10.11.3 (15D21)
Report Version: 11
Anonymous UUID: CEE925B9-5AA2-336C-5446-ECC3E274DFA6
Sleep/Wake UUID: 06A0FEF2-301D-49B9-8EE3-DE42DCF38FD4
Time Awake Since Boot: 1600000 seconds
Time Since Wake: 260000 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information:
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Invalid parameter not satisfying: windowNibPath'
Application Specific Backtrace 1:
0 CoreFoundation 0x92602f79 __raiseError + 201
1 libobjc.A.dylib 0x938b3fd1 objc_exception_throw + 276
2 CoreFoundation 0x92602dfa + + 138
3 Foundation 0x9b8d132b - + 118
4 AppKit 0x95187556 - + 161
5 Sparkle 0x0001c753 load_dsa_key + 12103
6 Sparkle 0x0001818d Sparkle + 20877
7 Sparkle 0x0001f1cf load_dsa_key + 22979
8 Sparkle 0x000207df load_dsa_key + 28627
9 Sparkle 0x0001733b Sparkle + 17211
10 CFNetwork 0x991d7d86 ___ZL32_NSURLConnectionDidFinishLoadingP16_CFURLConnectionPKv_block_invoke + 61
11 CFNetwork 0x991d2f5a __65-_block_invoke + 77
12 CFNetwork 0x991d2f05 - + 131
13 CFNetwork 0x991d2e65 - + 269
14 CFNetwork 0x991d2d3e - + 97
15 CFNetwork 0x991d7d44 _ZL32_NSURLConnectionDidFinishLoadingP16_CFURLConnectionPKv + 43
16 CFNetwork 0x991d7c92 ___ZN27URLConnectionClient_Classic26_delegate_didFinishLoadingEU13block_pointerFvvE_block_invoke + 110
17 CFNetwork 0x99373b84 ___ZN27URLConnectionClient_Classic18_withDelegateAsyncEPKcU13block_pointerFvP16_CFURLConnectionPK33CFURLConnectionClientCurrent_VMaxE_block_invoke_2 + 113
18 libdispatch.dylib 0x9339b763 _dispatch_client_callout + 50
19 libdispatch.dylib 0x933a9ec2 _dispatch_block_invoke + 459
20 libdispatch.dylib 0x933a9cf2 ___dispatch_block_create_block_invoke + 20
21 CFNetwork 0x991d2bd8 _ZN19RunloopBlockContext13_invoke_blockEPKvPv + 70
22 CoreFoundation 0x924c96a9 CFArrayApplyFunction + 57
23 CFNetwork 0x991d2ac1 _ZN19RunloopBlockContext7performEv + 141
24 CFNetwork 0x992ab5ba _ZThn16_N19RunloopBlockContext24multiplexerClientPerformEv + 20
25 CFNetwork 0x991d2954 _ZN17MultiplexerSource7performEv + 326
26 CFNetwork 0x991d276c _ZN17MultiplexerSource8_performEPv + 76
27 CoreFoundation 0x9250133f __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 15
28 CoreFoundation 0x924f2a1b __CFRunLoopDoSources0 + 523
29 CoreFoundation 0x924f1e42 __CFRunLoopRun + 994
30 CoreFoundation 0x924f17f6 CFRunLoopRunSpecific + 390
31 CoreFoundation 0x924f165b CFRunLoopRunInMode + 123
32 HIToolbox 0x948f92f1 RunCurrentEventLoopInMode + 267
33 HIToolbox 0x948f90f3 ReceiveNextEventCommon + 503
34 HIToolbox 0x948f8eec _BlockUntilNextEventMatchingListInModeWithFilter + 99
35 AppKit 0x94eed512 _DPSNextEvent + 1053
36 AppKit 0x952f80b0 - + 1057
37 AppKit 0x94eecf8b - + 121
38 AppKit 0x94ee212f - + 1063
39 AppKit 0x94e5d025 NSApplicationMain + 1630
40 wowhead-client 0x0000256b _start + 209
41 wowhead-client 0x00002499 start + 41
Clearing preferences did not help.
PS: Updating the Sparkle framework to the latest version fixed it, but updating frameworks is not for the faint of heart.
Post by
candreae
Or if you want... just copy paste this into Terminal, you can find the terminal application in your /Applications/Utilities/ folder
For US:
echo "set realmlist us.logon.worldofwarcraft.com" >> /Applications/World\ of\ Warcraft/realmlist.wtf
For EU:
echo "set realmlist eu.logon.worldofwarcraft.com" >> /Applications/World\ of\ Warcraft/realmlist.wtf
Fantastic...this was the easiest way for me...cheers!
Post by
Groovin
Just installed the client on Mac OS X 10.13. The three buttons on the right do not actually draw. There's no buttons (they function of course), just back text on the black background.
Post by
aprilleigh
Installed today and this was the result...
2017.10.26 10:13:03 PM: Authentication succeeded.
2017.10.26 10:13:03 PM: Checking for Wowhead Looter addon updates…
2017.10.26 10:13:03 PM: Looks like you're up-to-date!
2017.10.26 10:14:22 PM: Checking for supported realms…
2017.10.26 10:14:22 PM: No valid realm found.
2017.10.26 10:14:22 PM: This version of WoW uses an unsupported realm
Post by
Metushelah
Or if you want... just copy paste this into Terminal, you can find the terminal application in your /Applications/Utilities/ folder
For US:
echo "set realmlist us.logon.worldofwarcraft.com" >> /Applications/World\ of\ Warcraft/realmlist.wtf
For EU:
echo "set realmlist eu.logon.worldofwarcraft.com" >> /Applications/World\ of\ Warcraft/realmlist.wtf
This Worked for me, on the EU servers. Just restart your Wowhead client and do an upload.(##RESPBREAK##)2##DELIM##Sas148##DELIM##
Post Reply
You are not logged in. Please
log in
to post a reply or
register
if you don't already have an account.