Jump to content

whatbdt

Members
  • Posts

    2
  • Joined

  • Last visited

Posts posted by whatbdt

  1. 18 hours ago, Wolf_pd said:

    Because it is a BETA, it is unclear whether there is even an issue in FM, or it is just the BETA not working properly

    As long as it is a BETA, the SI devs can’t build a proper fix when needed.

    Rolling back is the only option if you want to continue and SI has offered support when that throws up errors.

    What more can do they do according to you?

    It's 100% an issue with the software not being implemented correctly for the beta as is clear in the error code; I have that much knowledge of appkit but unfortunately my knowledge stops at being able to fix it (and messing about with it would probably violate SI TOS anyway). Therefore the onus is on the devs to fix it; obviously they're not obligated to do this as it's unsupported software, I totally understand that. But I doubt it would be too difficult to do (devs, if you're reading, feel free to put me in my place if I'm wrong). 

    The Mac OS 14 Sonoma Public Beta is now available as of 2 days ago, meaning a very large percentage of Mac users will be upgrading or have already done so. The vast majority of these users will have no idea how to downgrade once they realise FM isn't working as Apple intentionally makes this difficult. It's in everyone's best interest to get this sorted. 

  2. Since the devs have no interest in fixing this, here's the error code:

    2023-07-14 02:06:19.808 fm[7856:118196] *** Assertion failure in -[NSMenuBarImpl setAsMainMenuBar], NSMenuBarImpl.m:674
    *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Main menu was determined to be visually equivalent, but the item index is out of bounds. This is invalid.'
    


    Outside of my realm of expertise but if anyone has any ideas let us know. 

×
×
  • Create New...