Problems in the new version of gdccdated

[papaloredsxd]

ungzip error:
TypeError: The encoded data was not valid.

[xBZZZZ]

TypeError: The encoded data was not valid.

That means unencoded save file (XML) is not valid UTF-8, that never happened to me.

Tell me which version and os (android or windows) of Geometry Dash generated the file and file name (CCGameManager.dat or CCLocalLevels.dat).

Compress the file to zip and attach zip, unless file is CCGameManager.dat and you are logged in and you don't want other people use your Geometry Dash account.

[papaloredsxd]

TypeError: The encoded data was not valid.

That means unencoded save file (XML) is not valid UTF-8, that never happened to me.

Tell me which version and os (android or windows) of Geometry Dash generated the file and file name (CCGameManager.dat or CCLocalLevels.dat).

Compress the file to zip and attach zip, unless file is CCGameManager.dat and you are logged in and you don't want other people use your Geometry Dash account.

@xBZZZZ

You're wrong, that's not it. It literally doesn't work. When I try an older version of gdccdated it works but in the current version of gdccdated it doesn't work.

[xBZZZZ]

When I try an older version of gdccdated it works but in the current version of gdccdated it doesn't work.

That's because older gdccdated used lossy UTF-8 parser that handles errors by emitting U+FFFD (�).
Newer gdccdated uses strict UTF-8 parser that handles errors by giving up.

Also why don't you send the not working save file? (my save files work (android, gd 2.2.13))

[papaloredsxd]

When I try an older version of gdccdated it works but in the current version of gdccdated it doesn't work.

That's because older gdccdated used lossy UTF-8 parser that handles errors by emitting U+FFFD (�). Newer gdccdated uses strict UTF-8 parser that handles errors by giving up.

Also why don't you send the not working save file? (my save files work (android, gd 2.2.13))

The ccgamemanager.dat of the gd 2.2 does not work in the lastest version of gdccadated but the ccgamenaager.dat of the gd 2.1 does work in the latest version of gdccadated, you should try to return the gdccadated to a previous version

[xBZZZZ]

try now

[papaloredsxd]

try now

bad UTF-8
code point offset inside data: 2823548
error offset inside code point: 0
data length:

[papaloredsxd]

downgrade the version of gdccdated to this version https://github.com/xBZZZZ/gdccdated/tree/7fc58401788a1e6d2b491a40e0a142113004a22b El 23 mar. 2024 19:05, "xBZZZZ" ***@***.***> escribió:

…

try now — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXHH2RNFYACSWIBAPAKO4Z3YZX4BTAVCNFSM6AAAAABE4U66ZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJWGYYTINBVGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[xBZZZZ]

bad UTF-8
code point offset inside data: 2823548
error offset inside code point: 0
data length:

click replace errors to behave like old gdccdated

but beware that saving will not keep broken UTF-8 (like old gdccdated)

---

also, is data length: actually empty for you or just copy+paste skill issue?

[papaloredsxd]

please downgrade the version of gdccdated to that version that I already told you https://github.com/xBZZZZ/gdccdated/tree/7fc58401788a1e6d2b491a40e0a142113004a22b El 25 mar. 2024 10:29, "xBZZZZ" ***@***.***> escribió:

…

bad UTF-8 code point offset inside data: 2823548 error offset inside code point: 0 data length: click replace errors to behave like old gdccdatedbut beware that saving will not keep broken UTF-8 (like old gdccdated) ------------------------------ also, is data length: actually empty for you or just copy+paste skill issue? — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXHH2RLSKWBWCU24U4N6QPLY2ARFFAVCNFSM6AAAAABE4U66ZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJYGAYTEMZQGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[xBZZZZ]

please downgrade the version of gdccdated to that version that I already told you
https://github.com/xBZZZZ/gdccdated/tree/7fc58401788a1e6d2b491a40e0a142113004a22b

why? does replace errors not behave like old version for you?
also why so old version? why not 6422943 (version before UTF-8 to js string (UTF-16) converter changes)?

[papaloredsxd]

Did you forget when I told you the reason? El 27 mar. 2024 5:01, "xBZZZZ" ***@***.***> escribió:

…

please downgrade the version of gdccdated to that version that I already told you https://github.com/xBZZZZ/gdccdated/tree/7fc58401788a1e6d2b491a40e0a142 113004a22b why? — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXHH2ROI5IHPJYVNFM7ZLQTY2JVE3AVCNFSM6AAAAABE4U66ZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRSGE2TSMBRGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[xBZZZZ]

ANSWER THIS FIRST:

does replace errors not behave like old gdccdated for you?

Did you forget when I told you the reason?

I think I found reason:

• The ccgamemanager.dat of the gd 2.2 does not work in the lastest version of gdccadated but the ccgamenaager.dat of the gd 2.1 does work in the latest version of gdccadated, you should try to return the gdccadated to a previous version

but that reason is outdated since e83b87f unless replace errors doesn't behave like old gdccdated

[papaloredsxd]

Yes, Please now downgrade the version of GDCCADATED to this version https://github.com/xBZZZZ/gdccdated/tree/7fc58401788a1e6d2b491a40e0a142113004a22b El miércoles, 27 de marzo de 2024, ***@***.***> escribió:

…

ANSWER THIS FIRST: does replace errors not behave like old gdccdated for you? Did you forget when I told you the reason? I think I found reason: - The ccgamemanager.dat of the gd 2.2 does not work in the lastest version of gdccadated but the ccgamenaager.dat of the gd 2.1 does work in the latest version of gdccadated, you should try to return the gdccadated to a previous version but that reason is outdated since e83b87f <e83b87f> unless replace errors doesn't behave like old gdccdated — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXHH2RIUJPRTQPSBP5FPTCTY2MGMTAVCNFSM6AAAAABE4U66ZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRTHAYTKNRSGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[xBZZZZ]

Yes

what happens when you click replace errors button in new gdccdated?

[papaloredsxd]

When I click on the "replace errors" button the file does load El miércoles, 27 de marzo de 2024, ***@***.***> escribió:

…

Yes what happens when you click replace errors button in new gdccdated? — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXHH2RPHXN3D2SEMRXAYY4TY2MRQNAVCNFSM6AAAAABE4U66ZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRTHE4TIOBWGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[papaloredsxd]

ccgamemanager.dat of the 1.9 does not load in gdccdated "xml parse error: Error: tag name is not <k> but <key>", I want you to add compatibility to the ccgamemanager.dat of the 1.9 in gdccdated El miércoles, 27 de marzo de 2024, ***@***.***> escribió:

…

Yes what happens when you click replace errors button in new gdccdated? — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXHH2RPHXN3D2SEMRXAYY4TY2MRQNAVCNFSM6AAAAABE4U66ZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRTHE4TIOBWGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[xBZZZZ]

is this correct?:

• both old gdccdated (6422943 (before UTF-8 strict)) and new gdccdated (e83b87f) with replace errors can load file but there is difference

---

reasons for asking (click to expand)

who	says what (not full text)
@papaloredsxd	When I try an older version of gdccdated it works
@xBZZZZ	does replace errors not behave like old gdccdated for you?
@papaloredsxd	Yes
@xBZZZZ	what happens when you click replace errors button in new gdccdated?
@papaloredsxd	When I click on the "replace errors" button the file does load

[papaloredsxd]

Yes El 28 mar. 2024 6:43, "xBZZZZ" ***@***.***> escribió:

…

is this correct?: - *both* old gdccdated (6422943 <6422943> (before UTF-8 strict)) and new gdccdated (e83b87f <e83b87f>) with replace errors can load file but there is difference ------------------------------ reasons for asking (click to expand) whosays what (not full text) @papaloredsxd <https://github.com/papaloredsxd> When I try an older version of gdccdated it works <#m_1635188539514375723_issuecomment-2010944030> @xBZZZZ <https://github.com/xBZZZZ> does replace errors not behave like old gdccdated for you? <#m_1635188539514375723_issuecomment-2023815621> @papaloredsxd <https://github.com/papaloredsxd> Yes <#m_1635188539514375723_issuecomment-2023978651> @xBZZZZ <https://github.com/xBZZZZ> what happens when you click replace errors button in new gdccdated? <#m_1635188539514375723_issuecomment-2023994860> @papaloredsxd <https://github.com/papaloredsxd> When I click on the "replace errors" button the file does load <#m_1635188539514375723_issuecomment-2024130202> — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXHH2RM2CRV2I3TPM4A5DLTY2PJ2PAVCNFSM6AAAAABE4U66ZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRUG44DINRTG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[xBZZZZ]

Yes

what is difference between:

• old gdccdated (6422943 (before UTF-8 strict))
• new gdccdated (e83b87f) with replace errors

?

[papaloredsxd]

The old gdccdated is better, please downgrade the version of gdccdated to this version right now https://github.com/xBZZZZ/gdccdated/tree/7fc58401788a1e6d2b491a40e0a142113004a22b El 29 mar. 2024 7:31, "xBZZZZ" ***@***.***> escribió:

…

Yes what is difference between: - old gdccdated (6422943 <6422943> (before UTF-8 strict)) - new gdccdated (e83b87f <e83b87f>) with replace errors ? — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXHH2RM47UVLWGZSSQZFASDY2UYH3AVCNFSM6AAAAABE4U66ZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRXGA2DGNBYGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[xBZZZZ]

The old gdccdated is better

answer not useful, need more precise difference

[papaloredsxd]

I already told you El 29 mar. 2024 18:44, "xBZZZZ" ***@***.***> escribió:

…

The old gdccdated is better what old gdccdated can do that new gdccdated can't? — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXHH2RLSHGCMU2B7ZPMKY5DY2XHEXAVCNFSM6AAAAABE4U66ZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRXG43DINZVGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[xBZZZZ]

I already told you

tell me again