You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ParseSwift uses PFObject instances for basically everything. All subclasses of PFObject are represented in MongoDB/PostgreSQL as collections/tables with given names. Mapping of the PFObject subclasses and their names in MongoDB/PostreSQL need to be known to Parse SDK so that PFObject subclasses can be loaded/stored properly to the database.
Prior to Xcode 16, there was no need to manually register any classes explicitly subclass PFSubclassing. After upgrading, the following error occurs when running the application: Thread 1: "The class My_App.MyParseSubclass must be registered with registerSubclass before using Parse."
🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.
New Issue Checklist
Issue Description
ParseSwift uses PFObject instances for basically everything. All subclasses of PFObject are represented in MongoDB/PostgreSQL as collections/tables with given names. Mapping of the PFObject subclasses and their names in MongoDB/PostreSQL need to be known to Parse SDK so that PFObject subclasses can be loaded/stored properly to the database.
Prior to Xcode 16, there was no need to manually register any classes explicitly subclass PFSubclassing. After upgrading, the following error occurs when running the application:
Thread 1: "The class My_App.MyParseSubclass must be registered with registerSubclass before using Parse."
Here is a link to a similar issue the Parse-SDK-iOS-OSX project: parse-community/Parse-SDK-iOS-OSX#1792
Steps to reproduce
Build and run an application with subclasses of PFSublassing using Xcode 16.
Actual Outcome
Thread 1: "The class My_App.MyParseSubclass must be registered with registerSubclass before using Parse."
Workaround
Manually register each object subclassing PFSubclassing directly after Parse Swift initialization:
Expected Outcome
App functioning properly without any subclassing errors.
Environment
Client
Server
Database
Logs
The text was updated successfully, but these errors were encountered: