In our ipad application user has to enter his details for registration. After user enter his details we save those details in the Device's keychain. So next time user launched the app user can use the app without registering again. Since we save it in the keychain even the app reinstall by deleting is also works fine.
To write to key chain we use sskeychain class as most developer do. This feature is working properly in devices without any issue.
One of our client use their symantec (unitymobile) mdm to distribute this app to their users. But when user install it through the mdm app gives following error when saving data to the key chain.
"The operation couldn’t be completed. (com.samsoffes.sskeychain error
-34018.)"
Initially we thought this is due to one of the policies they have included. But no luck. Can some one please tell me what has happened here and how to solve this issue.
P.S.
Actually underlying error was this.
(OSStatus error -34018 - client has neither application-identifier nor keychain-access-groups entitlements)
Related
How do I setup the pubnub cocoa objective-c client api to NOT store anything on the keychain? Is it possible to store the keys on the Application Support folder instead? When I am using XCode the keychain messagebox modal appears three times even when I press the 'Always Allow' button. It stops for a while but then after a few minutes it asks me again the same way again.
I've checked on my side and it really requested password for each read from Keychain. Tried to find solution and after system reboot, tried again - it requested for password one or three times and then just keep working. As for now, there is no option to configure client without Keychain usage.
Earlier Keychain worked like well after single password input. Looks like one of system updates broke how system interact with developed applications.
Maybe it is somehow related to security and checking "Automatically manage signing" and specifying proper profiles will help you (I'm unable to check this, since Keychain gives me access w/o asking password now since I marked awlays).
Keychain used to store few fields: publish sequence number, uuid, and push token. It had been added to Keychain to survive application re-install.
We will review macOS Keychain usage and if it will be allowed, we will add ability to use file-based data storage (maybe by default for macOS).
I was debugging my app in my personal Google play services account but the company I am working on has already got their Google play services account so I changed and DELETED (deleting api credentials and unpublished it) the game. I have managed to register a new android app but when I try to register a web app I get the error #4800004 (An unexpected error has occurred. Try again later).
What should I do?
It can take approx 7 days for your old package to be removed. You will not be able to add a new one until that happens.
Your options:
Wait 7 days and try again.
Rename your package.
Alternately: You cannot have two apps with the same package details. Are your two apps conflicting with each other?
From the github post, it was mentioned that you maybe re-registering an app with the same package name. You can check if your project was already registered in the console. Projects that you have deleted will take effect after the 7th day.
For further information, you can also try to check this page. It may also have something to do with SHA1 Signing Certificate Fingerprint from android studio.
You need to make sure that the LaunchURL that you provide includes the protocol (for example: http://) in addition to the domain. If you do not provide the protocol, google appears to automatically add https://, but this led to the error posted in the question for me.
I am a Google Glass application developer. During developing one application, I encountered some problems.
My application have landed on MyGlass and it's on review process, so it's not publicly visible. It only can be seen by me.
The problem is:
When I turn on my Glassware in MyGlass, my glass device never receive my application. Should I receive it or not? And why didn't I receive it?
I have launched the method mirror.accounts.insert.execute() from https://developers.google.com/glass/develop/gdk/authentication, and it didn't raise an exception, but I didn't receive the account information and the authToken on my glass device. This is because I haven't received my application on my glass device, am I right?
This is indeed correct: the token will only be sync'ed and available once the APK from MyGlass has been downloaded to your device and installed. After this first installation, you can safely replace the APK with a development one using adb install -r as long as it's using the same certificate.
Make sure to check that your device is connected to the internet, especially through WIFI. If that doesn't work, ask the Glass review team to help you out and check if there are any internal issues that would prevent your APK from being downloaded.
I am working on developing a Mac application that has an in app purchase. I have done this before on iOS, but I cannot get it to work with the Mac app. After doing some research it looks like I will have to get and validate a receipt from the Mac App Store before this will work.
I believe that I have followed the steps to do this correctly,
1.) Build the app in Xcode.
2.) Launch the app through finder
3.) When prompted sign in with a TestUser account created in iTunesConnect
4.) The app closes with the error message
“AppName” is damaged and can’t be opened. Delete “AppName” and download it again from the App Store.
When I open up the bundle though I do not see the _MASReceipt/receipt folder and file - and I am still getting invalid product identifiers from StoreKit.
These steps seems to work for me the last time this happened:
Log out from Mac App Store.
Force quit storeagent and softwareupdated processes.
Try double-clicking the app to start it again.
I am trying to submit my first application to the Mac App Store. I have setup the signing certificates on my computer, as well as setting up the application in iTunes connect. Xcode allows me to produce an archive of my app, and even export a signed pkg file. Both Application Loader and Xcode say that my binary passes "validation", but shortly after uploading my app to iTunes connect it is reported to have an "Invalid Binary." I read on Apple's iTunes Approval Process page some reasons why this might happen:
Appears when a binary is received through Application Loader, has been processed, but your binary is invalid. Examples of an invalid binary are: your binary icon does not meet our requirements, you have placed the payload directory at the wrong level in the .app wrapper, you attempted to use a non-increasing CFBundleVersion, etc.
Unfortunately I am not receiving an email when this error occurs, and nothing is telling me what the problem is. I am kind of hoping that Xcode would tell me if I signed my binary wrong in the "Validate" stage, but I may be wrong.
My question here is: why might iTunes connect be reporting an "Invalid Binary" and how on earth can I fix it?
EDIT: I have taken some screenshots of my project's configuration settings, and of iTunes connect:
iTunes connect app page
Application in the Archive list
Entitlements plist
Code signing settings
Info.plist
Build settings (architectures, etc).
You most likely are trying to submit a build that has the same version number as an earlier build. All builds that you upload to iTunes connect must have different version numbers. For example: Joe submits his first build of his app to iTunes connect as version 1.0, next time he submits he must change the version to 1.1 or any other higher value.