I have accepted Alastair Maw’s answer, as it was his suggestion and links that led me to a workable solution, but I am posting here some details of exactly what I did, for anyone else who may be trying to achieve something similar. As a reminder, in its simplest form my application comprises three assemblies: … Read more
I’ve had this problem and looked everywhere, including on Apple’s development forums. Apple will give a couple of stock replies, and that’s it. I think it’s a bug on Apple’s side. Validation locally on the device will work, so try to convert to that. If you absolutely must use server side validation, only transactionReceipt seems … Read more
“Can’t be done.” Running arbitrary (untrusted) scripts and staying safe is a contradiction. You should go as far as using custom kernels, jails, vms, the like. You can look at how http://codepad.org/about does it, it’s a lot of work.
Its seems they have moved this option to the “Status & Review” section. When accessing this section you will see this text: Do you want to make this app and all its live features available to the general public? And a button where you can change it to “Yes” or “No”.
I just ran into this same problem in my testing environment as well (luckily my live payments are going through). I fixed it by changing: public PayPalAPI(string specialAccount = “”) { System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls; to public PayPalAPI(string specialAccount = “”) { System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls12; They disabled support for SSL3 a while ago: https://www.paypal.com/uk/webapps/mpp/ssl-security-update, specifically stating … Read more
Some of these issues are currently being worked on. Some have been able to have been resolved by clearing the cache and cookies on your browser. This must be done prior to opening up the developer.paypal.com site and most developers have better luck with this when using Firefox or Chrome. There appear to be more … Read more
Kenny, you had the answer! For illustration I always think code is more helpful. //I do this in the didFinishPickingImage:(UIImage *)img method NSData* imageData = UIImageJPEGRepresentation(img, 1.0); //save to the default 100Apple(Camera Roll) folder. [imageData writeToFile:@”/private/var/mobile/Media/DCIM/100APPLE/customImageFilename.jpg” atomically:NO];
It depends on what you are trying to restrict. In general, publicly accessible API is not restricted. However, as long as you don’t grant the untrustworthy code the ReflectPermission(“suppressAccessChecks”) permission, it won’t be able to get access to non-public API in another package. If you have a list of packages to which you want to … Read more
When your app behaves in sandbox mode, it’s restricted compared to normal behaviour. In particular (quoting from the API docs for the sandbox): The API behaves as if the only users on Instagram were your sandbox users, and the only media ever posted were the last 20 for each of these users. So the API … Read more
Since the C standard is much too broad to be allowed, you would need to go the other way around: specify the minimum subset of C which you need, and try to implement that. Even ANSI C is already too complicated and allows unwanted behaviour. The aspect of C which is most problematic are the … Read more