EncodeBase64/DecodeBase64 Broken Between Real Studio and Xojo?

It seems that some things saved to a text file/database using EncodeBase64 in Carbon Real Studio will not properly load/open using DecodeBase64 in Xojo Cocoa, and vice versa.

Specifically a PDF encoded into Base64 using RS/Carbon doesn’t seem to properly decode using Xojo/Cocoa. The unaltered code works correctly for RS>RS and for Xojo>Xojo. Was there something specifically changed?

Nothing as far as I know.

In fact we used the same local SQlite database from RS in the first release of Xojo without issue and that was a change from RS to Xojo & from REALSQLdatabase to SqliteDatabase.

We had images in there.

Images seem to be working fine between the two, it’s just PDFs that are causing the issue. Is there maybe something related to the string encoding etc that could cause the differences between RS/Xojo?

We didn’t use any encoding parameters when decoding.

Literally none of the associated code was changed for this, so maybe a default encoding or something somewhere could be what’s causing the problem?

[quote=33524:@Oranged Software]Images seem to be working fine between the two, it’s just PDFs that are causing the issue. Is there maybe something related to the string encoding etc that could cause the differences between RS/Xojo?

We didn’t use any encoding parameters when decoding.

Literally none of the associated code was changed for this, so maybe a default encoding or something somewhere could be what’s causing the problem?[/quote]

There should be no encoding used since its a bunch of bytes and not a “string”
Theres nor reason I cant think of that an image would work and a PDF wouldn’t

Thank you. We found that our issue was not related to Encode/DecodeBase64, and was instead related to the change of EndOfLine going from chr(13) to chr(10) for Cocoa, as we were sanitizing some of the string after decoding.