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
Xcode shows "Ambiguous use of 'trackAppOpened' error when using ParseAnalytics.trackAppOpened as shown in Playgrounds, I have not been able to get it to work no matter what.
Steps to reproduce
In AppDelegate or anywhere enter the following code:
ParseAnalytics.trackAppOpened { result in
switch result {
case .success:
print("Saved analytics for app opened.")
case .failure(let error):
print(error)
}
}
Actual Outcome
"Ambiguous use of 'trackAppOpened'" error and build will fail
Expected Outcome
For it to not get an error and not fail
Environment
Client
Parse Swift SDK version: 4.14.2
Xcode version: 14.2
Operating system (iOS, macOS, watchOS, etc.): iOS
Operating system version: 15
Server
Parse Server version: 4.5.0
Operating system: No idea
Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): Remote
Database
System (MongoDB or Postgres): MongoDB
Database version: 3.6
Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): Remote
Logs
The text was updated successfully, but these errors were encountered:
🚀 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
Xcode shows "Ambiguous use of 'trackAppOpened' error when using ParseAnalytics.trackAppOpened as shown in Playgrounds, I have not been able to get it to work no matter what.
Steps to reproduce
In AppDelegate or anywhere enter the following code:
Actual Outcome
"Ambiguous use of 'trackAppOpened'" error and build will fail
Expected Outcome
For it to not get an error and not fail
Environment
Client
4.14.2
14.2
iOS
15
Server
4.5.0
No idea
Remote
Database
MongoDB
3.6
Remote
Logs
The text was updated successfully, but these errors were encountered: