PFActionButton configuration property conflicts with UIButton in iOS 15

[bcbeta]

@property (nonatomic, strong) PFActionButtonConfiguration *configuration;

gives error:

Auto property synthesis will not synthesize property 'configuration'; it will be implemented by its superclass, use @dynamic to acknowledge intention

and

Use of undeclared identifier '_configuration'; did you mean 'configuration'?

[davewhipps]

I'd just like to 'upvote' this. Apple automatically updated XCode last night, and the new/latest (iOS 15) SDK breaks this. I'm using the cocoapod, so my app won't build and I'm stuck in the water.

[idefen1]

I'd just like to 'upvote' this. Apple automatically updated XCode last night, and the new/latest (iOS 15) SDK breaks this. I'm using the cocoapod, so my app won't build and I'm stuck in the water.

same here =*(

Just a quick update, if you don't use PFActionButton in your project, just 'accept' the change and it builds / runs correctly. Hope this helps.

[gorillatapstudio]

Let's just change it from configuration to config to have a quick fix.

[ashish-naik]

@bcbeta @davewhipps @gorillatapstudio @idefen1 Till the time official fix arrives, one solution is to download previous version of xcode from download page.

Once downloaded, unzip the file and rename it to add version number and move it to Applications folder. Renaming required so as to not overwrite version that exists in Applications folder.

Open this version, go to Preferences -> Locations and set command line tools version if you build from command line using tools such as fastlane or your own build script.

I tried and was able to compile and run the app without any issues.

You may have more than two versions as long as enough disk space is available.

This article explains in details as well.

Hope this helps.

[mxnmike]

@cbaker6 you closed the issue on parse-community/Parse-Swift#244 and now you closed this one, so will be any fix coming soon?

[cbaker6]

This issue is currently open. The ParseSwift issue was closed because the comment you left was unrelated to that SDK.

[mxnmike]

This is my first time commenting so i dont know what you mean about that, but, will there be a fix in the near time?

[cbaker6]

@mxnmike near the title of each issue, there’s a label that’s green and says open. If it’s closed it will be red and say closed. This one is currently open.

I recommend looking at the linked pull request. If you are able to help, you can provide suggestions either there or in this issue thread depending on the context of your suggestion.

As I’m not the maintainer of this repo (I just help out), I don’t know when it will be fixed. If you ask questions related to ParseSwift on the ParseSwift repo, I generally answer those as I maintain that repo.