We have developed a Facebook Canvas App, and using the test version, we create test users who can successfully install and test the app.
Here's the thing. Using the production version of the app (not yet approved by Facebook), and using test users created under this version, when I try and install the app to the user I get the error message "User is not allowed to see the application.: The user is not allowed to see this application per the developer set configuration."
I have made sure I am not logged in as another test user, I've cleared the cache prior to logging in as the test user, etc.
As near as I can tell, test users created under the production version should be able install the app and test it, correct?
If not, then when you submit the app for Facebook Approval, what accounts will the use?
Thanks!!
Here's an explanation:
Created test users under the test app won't be able to use the prod app, just as Created test users under the prod app won't be able to use the test app.
Real users, added as TESTERS of the prod app, should be added manually as testers of the Test App.
Related
I have a commercial macOS app I distribute in the Mac App Store. Now at startup I check for the App Store receipt and exit with code 173 if it is not present. This brings up the App Store sign in dialog in order to get a receipt.
I have always tested this with sandbox accounts but now I only get errors when I try to sign in with a sandbox account (or my real Apple ID).
The issue emerges when I start from XCode as well as when I export the app as a development build.
I have the following setup:
macOS 10.15.1
XCode 11.2
App signed with valid development certificate
I have tried the following:
Sign out of App Store app
Restart Mac
Tripple verified email and password
Create new sandbox user in App Store Connect
Ran codesign -vvvv which reports everything is fine
I do, however, see the following error on the Console, but could not figure out what it is supposed to mean:
StoreLegacy: Failed to perform in-line receipt renewal for application
at path /Users/me/Library/Developer/Xcode/DerivedData/MyApp-alwjuasqcasdfaufnnxhqeoo/Build/Products/Debug/MyApp.app :
'Error Domain=com.apple.commerce.client Code=600 "(null)"'
Has anybody seen this before?
Update
It works as expected on Mojave. So I assume this is an issue with Catalina.
#codingFriend1 - Thanks. I should have posted the workaround. It seems the problem was that I'm in the UK and my test account was with the UK app store. I created a new tester with the US app store and that worked.
The resulting certificate works with UK tester. I don't think it used to be like this, but hey ho!
It was this that finally got it working for me but there may be other problems.
My Enterprise application is having more than 1000 users in production. Yesterday my provisioning profile got expired. From yesterday I got many calls of users that they did not able to use their app.
Is there any way so that the existing user don't need to install the new build again. Because its very difficult to tell more than 1000 users to reinstall the app again.
Please help me. The issue is with production.
Unfortunately, you will need to get the new provisioning profile on the devices somehow. The provisioning profile must get on the device, and you can simply provide the new profile by itself, or you can rebuild the app and the profile will be included in the app's payload.
There are a couple of ways to do this, but here are the most popular methods:
If the devices are managed using an MDM product, you can push the new profile out to the devices using the MDM capabilities. Again, you can use the MDM system to push just the provisioning profile, or you can push the new app build with the new provisioning profile. Judging by the fact that you would be requesting users to re-download the app, I don't believe you are using MDM to manage the devices.
If you have older devices (iOS 7 and before), you can have the user manually install the new profile. You can email the provisioning profile to the users, and they will be able to open the profiles on their device. Or you can host the profile on a web server and direct the users to open the link to install the profile. The app will then work with the new, valid profile.
Rebuild the app and re-distribute. When the users download the app (or any other apps built with the profile if you are using a wildcard identifier on your profile), the new profile should replace the other one and the app will be able to launch.
Unfortunately, all of these methods require you to get the new profile downloaded from the developer site onto each of those devices.
I have downloaded an example of Facebook Application using PHP sdk, and it is working well when I access it from the account that admin that application but when I try to access it from another account I got an error message
please any help
Check the Sandbox Mode for the app on https://developers.facebook.com
This restricts the application to developers.
We have an app in the store right now that was shipped with a wildcard app ID.
The update that is now pending approval was created with an explicit app ID, to enable push notifications.
We've noticed the following issue during ad hoc testing of the update: if we delete the app-store version from our iPhones, and then install the ad-hoc update, everything is fine. If, however, we leave the app-store version running in the background, and install the ad-hoc update over it, the updated version installs but fails to start up. We suspect that this has to do with the ID change.
If this problem is specific to ad hoc installs, then it is not a worry for us, but we are concerned that existing users will encounter this problem when doing the real upgrade from the app store.
Has anyone seen installation issues after upgrading from a wildcard-ID app to an explicit-ID version?
I'm building an iOS app that uses push notifications, and I'm finally ready to submit it. Before I do, I'd like to test out push notifications off the Production server, to make sure everything is working correctly. Thus far, the sandbox environment has been working fine.
After doing quite a bit of searching, I learned that switching the servers over from ssl://gateway.sandbox.push.apple.com:2195 to ssl://gateway.push.apple.com:2195 wasn't enough, and that production push tokens are different from sandbox push tokens. Instead, apparently I need a new provisioning profile with Production entitlements, new certs installed on my server, and to re-build my app with said profile so that it knows to create the correct push tokens.
So, after going through all the steps, I can't even make a build run on my phone; XCode says
This profile cannot be installed on devices
Here are the steps I've taken. If I'm missing something please let me know:
In my iOS Developer Center, I've made sure that my AppID is "enabled for production" under the Apple Push Notification Service.
Also in my iOS Developer Center, I've created my Production Push SSL Certificate, gone through the necessary conversion steps, and installed the resulting .pem on my server.
Per the instructions, I've create "a new provisioning profile containing the App ID you wish to use for notifications." I've done this by going to Provisioning, and clicking on the "Distribution" tab, and making a new profile. I've confirmed that "production" is set under the "entitlements" section of this profile.
I've selected the provisioning profile in my project settings. I get the message
This profile cannot be installed on devices
and I'm stuck.
Build an ad-hoc distribution version of your app, and install it on your own device. That will use the production APN gateway and certs.
You cannot install an app compiled with a appstore distribution (production) profile on a device. Only Apple reviewers can do that. you can only test push on an app compiled in development mode and using sandbox server.
If you want to test production servers, you must compile the app using an AdHoc distribution profile enabling the devices you want to do the test. Clearly you must recompile and the send the app for review using the App Store distribution profile.