Ken rebound #99535

https://thebrain.zendesk.com/agent/tickets/99535?brand_id=169034

Hello Ken,

I understand your expectation here, so I want to be very clear and transparent.

We have already reviewed the Output.log internally, including by engineering. In this case, the log does not contain the attachment filename that is triggering the warning. There isn’t another team or tool we can refer this to that would be able to extract a filename that simply isn’t present in the log data.

At the moment, the application does not surface the specific attachment name for this error, either in the UI or in the logs. Because of that limitation, there is no way for us to email you the filename directly.

That leaves only two viable ways forward:

If you suspect which attachment may be involved, rename that file to remove special characters and retry the sync.
If the attachment is unknown, the only reliable resolution is to correct it on a desktop using a Data Integrity Scan:

Export the Brain as a .brz from the iPad
Import it on a desktop computer
Run File > Utilities > Data Integrity Scan and correct the unsafe attachment name
Sync the Brain to the cloud
Delete the local copy on the iPad and download it again

I know this is not ideal, but given the current logging behavior, these are the only methods available to resolve the issue.

If you do not currently have access to a desktop machine, please let me know and we can discuss timing or alternatives, but there isn’t a way for us to extract the filename directly from the log.

Best regards,

John