I'm trying to create an App on https://developers.pinterest.com/apps/
The App state is still "in development" and the hint says I need at least 1 more collaborators allthough I already have three.
Furthermore, uploading an image as App Icon causes a JS error in the App Management Page ("Error" and http state 500)
How to get over that obstacles:
Define the app with all necessary settings like devs, testers and an Icon?
Related
I created my app with Shopify CLI "shopify create" (Node.js app) and deployed it to Heroku (shopify deploy). I already add my .env variables (scopes ,SHOPIFY_API_KEY, SHOPIFY_SECRET_KEY, host, shop) to my heroku config Vars, and I changed my app url to https://MY-URL.herokuapp.com/ , and the whitelisted redirect urls to https://MY-URL.herokuapp.com/auth/callback
When trying to open the app in my dev store, the interface is shown correctly (see image below)
However, the interface is unresponsive. So e.g. I can not press the button or select the text with mouse. (actually I can not do any mouse actions at all)
I have no idea what could cause this unresponsiveness.
Further info:
If i open https://MY-URL.herokuapp.com/ in browser, Safari says "Safari cant find the server, "https:undefined/admin/oauth/authorize?...",
Chrome says "
This site can’t be reached
Check if there is a typo in undefined.
DNS_PROBE_FINISHED_NXDOMAIN"
I deployed the app a few hours ago (~4 hours) .
Thank you in advance, any help is appreciated.
I am finishing an app that allows users to submit feedback to an iCloud Container. In order to simplify the process of retrieving that feedback, and to protect privacy, I have created another app to read those submissions. This app will be private and not uploaded to the App Store. This requires that both apps be able to access the same iCloud Container. Therefore, both apps have entitlements with their iCloud Container identifier set to the same value:
iCloud.com.myDomain.My-App
For clarity I refer to the first app as My App and the second as My App Feedback.
When I try and run My App Feedback to read the feedback, Xcode gives an error:
Couldn't get container configuration from the server for container "iCloud.com.myDomain.My-App-Feedback"
It appears that even though I have set the app entitlements iCloud Container identifier for both apps to My App, Xcode is using the app Bundle Identifier instead.
Is there a way to override that behavior so that both apps can access the iCloud data?
If you have selected the correct container in the entitlements, then just make sure when you set your CloudKit Container in code from within My App Feedback that you are specifying the correct one:
let container = CKContainer(identifier: "iCloud.com.myDomain.My-App")
and not either of these:
let container = CKContainer(identifier: "iCloud.com.myDomain.My-App-Feedback")
let container = CKContainer.default() //This should work, but might be using the wrong one
You could confirm which container is being selected by printing it to the console when it gets instantiated. Hopefully that helps.
Try using CKContainer(identifier: "iCloud.name_of_your_container") instead of CKContainer.default()
I named my Cloudkit container testapp and my app's bundle id was com.my_team_name.testapp. When running Cloudkit queries, I kept getting this error:
Couldn't get container configuration from the server for container "iCloud.com.my_team_name.testapp"
After looking at the Cloudkit Dashboard I realized that my container's name was literally only "testapp."
Changed my code to CKContainer(identifier: "iCloud.testapp"). Worked just fine.
I am trying to upload hosted content for in-app purchases, however I have been unable to succeed so far.
I have previously uploaded around 100 in-app purchases packages for my app using Application Loader. I used to be able to upload these packages before without any issues. Now I’ve noticed that the latest version of Application Loader (Version 3.0) doesn’t even give me the option to upload hosted content (see attached)?
So instead I’ve taken the time to use the iTMSTransporter bash script instead. However when I try to upload the content packs using:
iTMSTransporter -m upload
I am getting the following error:
Package Summary:
1 package(s) were not verified because they had problems:
/Users/Cortana/Documents/iOS/Clients/AccentKit/InAppContent/854413379.itmsp - Error Messages:
ERROR ITMS-90320: "The archive for In-App Purchase 'com.accentkit.AustraliaFemale1' is invalid. The 'IAPProductIdentifier' in the ContentInfo.plist must match the In-App Purchase Product ID."
[2018-04-14 07:12:45 MYT] DBG-X: Returning 1
I’ve double checked and the value for IAPProductIdentifier on the ContentInfo.plist matches exactly with what’s setup on the In-App Purchase Product ID on iTunesConnect. (see attached screenshots) This error is making no sense to me.
Any ideas?
If there was an issue with banking and your sales contract are according to you theoretically back in effect, they may not be effectively back in effect, that is, from Apple's servers point of view.
perhaps this is a process that takes up to a week and the only way to speed it up is to call their technical support.
this is where that'll happen : https://developer.apple.com/support/technical/
I suspect it's likely that your app having been on monetary lockdown at any one point while the bank was an issue may have led into this buggy situation that apple may not have accounted for or that they have accounted for and want you to first go through their IT support process in order for them to first be able to asses that everything is in order.
cheers! :)
If locationServicesEnabled() == false, I'm prompting the user to enable their Location Services. The following URL works for 10.0+, redirecting the user to the Settings app and directly to the Location Services screen:
URL(string: "App-Prefs:root=Privacy&path=LOCATION")
However this doesn't work in iOS 11. It opens the Settings app, but doesn't drill down to the Location Services. Anyone knows what's the new URL for iOS 11+?
I am experiencing the same issue since the first beta releases. I've tested a lot of different schemas but none of them worked properly. In the first releases opening schemas would redirect to the home screen but they already fixed that.
Open Location Services:
If this app is for personal use only and you do not plan to submit it to the App Store, then you should be ok to use the following. Otherwise, if you do plan to release your app, Apple will reject it upon review. Code is:
UIApplication.shared.open(URL(string: "App-prefs:LOCATION_SERVICES")!)
I'm trying to make an App Extension for the Mac that accesses the current users calendars, but it doesn't seem to work. Am I missing something?
I added the Calendar app data capability to the extension (and the main app to see it it would make any difference -- it didn't). I have the following code in my extension:
EKEventStore* store = [[EKEventStore alloc] init];
It doesn't even get to the requestAccessToEntityType:completion: method (next line) before throwing an error into the console:
serviceName = "com.apple.CalendarAgent.database";
} ... returned error Error Domain=NSCocoaErrorDomain Code=134070 "An error occurred in the persistent store." UserInfo=0x61000026dd80 {Problem=request failed, insufficient permission} with userInfo dictionary {
Problem = "request failed, insufficient permission";
The documentation says that I can't use APIs "marked in header files with the NS_EXTENSION_UNAVAILABLE macro" (no such macros are in the header). It does say "the HealthKit framework and EventKit UI framework are unavailable to app extensions" but EventKit is not "EventKit UI framework" which is iOS only as far as I can tell.
My guess is that there's a problem showing the permissions dialog. Does Apple's Calendar Today Widget have special permissions that third-party apps can't access?
Does Apple's Calendar Today Widget have special permissions that third-party apps can't access?
it is an apple app and doesn't need to worry about permissions AFAIK
but:
from reading the docs regarding core location I understand that the extension can only use GPS after the user approved it for the app -- I would transfer it to the calendar access! => ergo - in my eyes: it works in the app but not in the ext then it is a bug