-
Notifications
You must be signed in to change notification settings - Fork 443
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warning when uploading App #672
Comments
Hi @macintosh-HD ! I'll do some investigating here - which branch of CareKit are you using? |
Hi @gavirawson-apple, sorry for the late response. We are using the main branch. |
Thanks! I'll do some digging and get back to you. |
Are you able to upload your app to the App Store despite this warning? Or is it blocking you from uploading the app? |
Gavi,
I also receive this warning. I can successfully upload my app to Connect
for TestFlight use, but have not tried getting approval for release on the
App Store.
Thanks,
Dave
…On Thu, Nov 17, 2022 at 10:00 AM Gavi Rawson ***@***.***> wrote:
Are you able to upload your app to the App Store despite this warning? Or
is it blocking you from uploading the app?
—
Reply to this email directly, view it on GitHub
<#672 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKEBNHKKMZ2CVOBZKOC2NALWIZQCPANCNFSM6AAAAAARG4Q32M>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Thanks @drdavec, it's helpful to know how many folks are impacted by this issue. Let me know if this becomes a blocker for uploading your apps to the App Store. At the moment this seems to me like it's not specific to CareKit, and may get ironed out in Xcode. But let me know if this does become a big blocking issue. |
It may help you to figure out the issue. |
Hi,
recently I get warnings when uploading my App to AppStore Connect. The logs say:
I don't have a function with that name in my app.
Upon further investigation I found that CareKit implements such function in the
OCKContactViewController
and it is private.I only got the warning after switching to Xcode 14.
Is it possible to make that function public to resolve the warning?
The text was updated successfully, but these errors were encountered: