After a lot of digging we have paypal adaptive payments working in the sandbox with embedded/chained payments using the paypal_adaptive gem. Now the time has come to try out the live payment system, and as far as I can tell it seems that paypal is no longer giving out the X-PAYPAL-APPLICATION-ID needed to use the service (?).
The submission process described in this thread no longer seems to exist, and eventually I noticed this message in the sidebar :
The application submission form and application management tools (MyApps) for PayPal apps are currently offline so that we can launch a new and improved tool.
If you have questions about your app that has already been submitted, please select the "What's Up with My App?" option on our contact form.
We appreciate your patience while we work to improve x.com.
We've invested a reasonable amount of time getting everything working via the sandbox, and there was no indication during this time that the live service was unusable, though in hindsight we should have picked this up sooner. Nor can I find any information as to when this happened, and how long it's expected to be offline for.
I have sent a mail via the support system but am yet to hear back - does anyone have any idea what's going on with the adaptive payments service or when it might be available again, or if there's any other way to apply for an X-PAYPAL-APPLICATION-ID?
It came back up last night.
Despite repeated attempts by me and other members of paypal's dev community, we didn't get a concrete date until it was back up (I only noticed because I check every morning).
You can fill in an application here: https://www.x.com/user/my-account/applications/new
Depending on how advanced your integration is, they will generally give you a live AppID and approve the app automatically, then a human will review your app in the next 2 days or so - although I would suppose that there is a bit of an avalanche of app submissions going on at the moment so they might take a bit longer.
as an aside: strangely enough it was me that posted the original question that #recurser linked to, I guess this explains the 500 views :)
After some more digging, it appears that it is scheduled to return November 7th~8th.
Its already Nov 15 and it still is offline, after spending almost 2 days on this i havent found any response from paypal people.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 3 years ago.
Improve this question
My app was rejected. We appealed one week ago this Friday, including documentation and some screen shots.
We have heard nothing back yet. I received an email that they did receive the appeal.
How long does Apple take to review an appeal?
Usually the apple review team responds in 24 to 48 hours after appealing. Although this time may vary depends on the complexity of your case.
My suggestion is do not ping them too much & if you have submitted an appeal. Keep it patient & wait for at least few days. They will surely respond on time.
Another most important thing is you should keep using good & kind language tone while communicating to the review team. Other wise it can be the worst case & you can get your account suspension.
So my suggestion is be kind & patient.
Important Note :
This suggestions I am giving based on my past experience just to make sure anyone could not face such weird issue again.
What happened in my case was my application was not getting into review since more than 20 days. I kept messaging them & asking about the status. I even appealed them why it's getting much delayed. Every time I got response like review team is working hard & your app will be reviewed soon.
At one stage I loose my temper & I have given them examples of the other publishers who get their apps live even after they have uploaded their apps. Apple review team found this behaviour bit rude & sadly it ended up with suspension of my account permanently. It was a huge loss as there was few live stable apps all got removed from store due to suspension.
Hope this helps to everyone.
I am building out a iOS & Android app. My app may not fully scale to support users and have some limited functionality out the gates. I wanted to put an invite list on the front of registration like Mailbox did a few years ago.
I was trying to read the Apple app store guidelines to creating a "waiting list / invite list" and couldn't get a clear picture. I assume Android is more flexible on this, so I figured I could start with Apple's guidelines first.
Here is what I can find.
In Apple's docs, it says under 3.2.2 "UnAcceptable"
(v) Arbitrarily restricting who may use the app, such as by location or carrier.
In this specific case, I am not blocking by location or carrier. I am just putting up a wall to use the app since some of my users can use it in a limited form, but I can't open it up to everyone on Day 1.
I understand I can run a "testflight" release, but I wanted to make our app available in the App Store for anyone to download since it will be publicly available, just not fully ready for a million people to hit it. My understanding is that the testflight release requires a bit more work based on their docs and isn't as simple as just putting it in the public app store so anyone can get to it.
Apple has the ultimate authority for approving and rejecting apps in their app store so nothing on SO can really be perfect advice. If you are really concerned about approval, you can try to contact apple developers support. Here are a few things I would advise:
Make sure in the developer notes for Apple when you submit to them you include a free account.
In the notes for the app store let the users know that it may take up to __ hours for their registration to get activated.
My understanding is you are doing this to handle the volume of users as you are launching the app. Be advised though that if you start restricting users too much you will possibly get poor reviews. Only restrict usage if absolutely required. If you run into issues make sure you are communicating with the users so they understand.
Good luck with you new app!
BACKGROUND
I'm helping a 3rd party host 3 apps that they paid me to write (they've given me access to their Apple credentials - created expressly for this app - in order to manage the iTunesConnect process).
Because of this, I get access to all of the sales data, etc. through iTunesConnect. We currently have all 3 apps released, two of which are first-time releases and one of which has been on the store for a few months and updated a couple of times. The first app was initially released with a $1.99 price point as an introductory price, which went up to $3.99 after about a month.
ACTUAL QUESTION
I just got my daily report from AppFigures.com (highly recommended, by the way; it's a relatively cheap way to get a good amount of automated data and analytics about app sales), and I noticed that app #1 had 3 refunds yesterday. We've only had 7 refunds ever, and all 3 of these refunds were originally purchased at the $1.99 price point. Therefore, this has made me very curious as to why they got the refund NOW. We had bugs earlier on that have subsequently been resolved by updates, so I don't understand why someone would have a legitimate reason to ask for and receive a refund at this point.
Please note: I'm fully aware that I'll never get the information to tie back directly to the user. I understand why, but it's a bit of a shame (and it's why we included a voluntary contact/feedback mechanism in the app itself). I'm just wondering if I can see from Apple the reason they selected for requesting the refund.
Basically, I'd like to answer the following question:
"Why did Apple think it was justified to refund this user's money?"
I'm guessing it would be a helpful piece of information for us; if there's something wrong with the app and we're not aware, this could help us fix it. Does anybody know how/if that information is available?
I did what Injuanj suggested and contacted Apple directly.
Here's their (completely unhelpful) response:
Thank you for contacting us about your Sales and Trends reports.
I understand that you are wanting more information regarding refunds.
You can find Refund information for your content by filtering your Top
Content dashboard to Transaction Type > Refund. Refunds will be
indicated as negative values.
Apple does not provide customer or refund information at this time.
If you have further questions regarding your sales reports, please let
us know. We're happy to help.
Best regards,
Julie
iTunes Provider Support
I already knew how to view my refund/return count, which is how I knew to send the email in the first place!
I didn't ask for customer information. I know Apple's not going to give that. Duh. I actually specified this in my original email.
I guess the real answer here is this:
Apple does not provide customer or refund information at this time.
under the 'practical, answerable problems that are unique to software development'- specifically iOS development...
I give you the following:
I'm specifically asking about how Apple/App Store handles the following issue: namely, who receives updates when I reduce the number of territories in which my app is sold.
For example, currently my app is sold in every territory around the world. For my next release, I want to reduce the territories to just one (my own country).
My question is: what happens to the users from the other countries who have already downloaded my app? Will they continue to receive updates (as I will continue to release updates for my own country/territory)? Or will they remain 'paused' on that final version of my app that was available in their own territory, in other words, effectively 'locked-out' of further updates?
I did attempt to research this issue before asking this question and while the two links below certainly 'overlap' my question, I'm still confused about what precisely happens.
If you do know the answer - and let me know - I'd be very grateful!
Best regards, John.
Research. Prior questions that were tangentially related to the IOS programming and app development environment. Please take a moment to consider the overall utility of this question before banning for being 'off topic'. I am not talking about planting geraniums here - I'm talking about something that is - or should be - of interest to coders and developers.
iTunes Connect App Update release for all countries?
Updating an iOS app in one territory only
Anyone who has already purchased (even if free) your app will continue to be able to download it forever. If you update the version, they get the new version, not the old one (unless you change the is version require to - then they get the newest one supported by their OS version.
If you pull an app completely (from all markets) you can flag it as being "for legal reasons". this prevents it from being re-downloaded, even from people who already purchased it. But this takes it off all markets, not just some of them.
It sounds like you need to contact Apple directly and describe why you want existing customers to have their right to access your app taken away. Maybe they can make a special case. In general though, they don't allow it.
I'm starting making an app for a website that I own. I know some about programming with xcode but there's a lot of stuff that I don't know yet. Mostly I have almost everything figured out for the app but I need to add to the app a way to sign in and sign up to the website and also a way to pay with credit card. I don't know how to start with all that.
I have tried to look some videos but I didn't see anything similar to what I want to do. I would really appreciate if you could explain me it, or send me some kind of help.
While I can't help you with sign-up/in features, I do know that ZooZ seems to be the cheapest and easiest way to accept credit card payments on mobile apps.
Both iOS and Android compatible, ZooZ's 3 lines of code monetizes your app in minutes. Users have their choice of checking out with credit cards or PayPal.
The biggest advantages of ZooZ are that your user always stays within your app and won't have to re-enter payment details in the future, resulting in faster processing and higher conversion rates.
Of course you can always build your own credit card processing platform, but considering the challenges of security, merchant accounts, and PCI compliance, it's probably not worth the headache.
Full disclosure: I have the privilege of working at ZooZ :)
Good luck with your app!