Base64Decode/Encode does not return same result when file name is not specified (8 Comments)

Issue report by Jeremy Bante

Product

FileMaker Pro

Version

14

Operating system version

OS X 10.10.3

Description of the issue

Given an original base 64 text, the Base64Decode function does not return the same container result when a file name is not specified vs. when a file name is (and beyond just the file name applied to the container data). When Base64Encode is then applied to the container value that was created without a file name, the result is different from when encoding data originally decoded with a file name specified, and not even the same length.

Steps to reproduce the problem

Use the Base64Decode function to decode the same base 64 data, both with and without a file name specified, then use the Base64Encode function to re-encode the data.

Expected result

The result of Base64Encode ( Base64Decode ( ... ) ) should be identical when the same base 64 is specified, but any different file name or no file name at all is supplied to Base64Decode. Except for the file name, the result of the Base64Decode function should display in a container field the same when the file name is not specified as when the file name is specified.

Actual result

Base64Encode ( Base64Decode ( $base64 ) ) produces a wildly different result from Base64Encode ( Base64Decode ( $base64 ; "file.ext" ) ). Base64Decode ( $base64 ) and Base64Decode ( $base64 ; "file.ext" ) results display differently in container fields.

Configuration information

Here is an example file demonstrating the problem: https://www.dropbox.com/s/n3m0yalqainlq6b/Base%2064%20Behavior.fmp12.zip?dl=0