Jump to content
You must now use your email address to sign in [click for more info] ×

Search the Community

Showing results for tags 'document access'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Staff and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.5 Beta New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Member Title

Found 1 result

  1. MacBook Pro16 10.15.3, AFPUB 1.8.3. Document Resource folder and Documents are all on the local laptop System Drive (SSD). I have to believe that it is a real bug. It happens randomly and I cannot replicate it reliably. Scenario: Have two documents open (cover, and main document for a book). I modify the cover a bit and save it to the local system disk on the mac. I modify the main document with changed text in an existing text frame. I save that with Command/S. Then I go back to the cover and export the two pages to PDF. Then I close only the Cover document with Command/W. I think that might be the trigger for the next event - a sort of crash. So just the main document is open and I add some indexing to the changed text and press command/S to save. The progress bar appears and then, a second or so later, a critical message pops up (attached). The message does not make sense - "access to the document file was lost while performing initial loading." Why would an open document that was just saved 2 minutes ago lose access from the local system disk and why would it be performing "initial loading"? After I click "OK" to close the message, the document disappears, the progress bar is locked at max, not progressing, and AFPUB has to be Forced Quit since it stops responding. The very unusual thing is that it appears that the document was actually saved properly (short save since it was only a small edit), then AFPUB threw a fit.
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.