Apple DTD PLIST error
I created a bedrock server with version 1.8.0.24 ,and this morning ,
The server suddenly showed this infomation,
then all player disconnected from server and can't connect again,
untill i restart the bedrock server .
the cpu usage is higher than before
bug snapshot is showed in picture
<?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>id</key>
<string>0</string>
<key>delay</key>
<integer>0</integer>
<key>status</key>
<integer>0</integer>
</dict>
</plist>
Attachments1
Created Issue:
Apple DTD PLIST error
I created a bedrock server with version 1.8.0.24 ,and this morning ,
The server suddenly showed this infomation,
then all player disconnected from server and can't connect again,
untill i restart the bedrock server .the cpu usage is higher than before
bug snapshot is showed in picture<?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>id</key>
<string>0</string>
<key>delay</key>
<integer>0</integer>
<key>status</key>
<integer>0</integer>
</dict>
</plist>
Attachments1
- Unresolved
- Open
- Unconfirmed
- Windows
- ubuntu18.04
- 1.8.0
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
MCPE-40337 → 
BDS-349![[Mod] OcelotOnesie](../../../data/avatars/users/43220.png){kind=small}
I have intermittently seen this issue as well, on both 1.7.0.13 and 1.8.0.24 (Ubuntu). When this occurs for me, the server process exits as soon as the plist error is logged.
I just experienced this error for the first time, too. Thought it was very weird, never seen it before. I had to restart the server and everything was fine again. Running on Ubuntu 18.04, Bedrock 1.9.
I know why it happend, i enabled the whitelist,and add a wrong xbox id ,the bds server can't find this xbox id's uid with mojang api ,and shutdown
Thank you for your report!
Crashes such as these are now logged automatically, this will therefore be investigated further by the development team internally.
I realize this response might seem silly after 12 months, I am working my way through the backlog of BDS tickets to clear it out and get a clear picture of the outstanding issues with BDS.
Please note though that while the bug report will be closed, BDS does forward crash data on to Mojang which is investigated seperately to the bug tracker.
Ionic
Quick Links:
đ Issue Guidelines – đŹ Community Support – đ§ Customer Support – đ BDS Wiki – đ FAQs