Newsstand App rejected - in-app purchase issue

Similar Questions

• In-App purchase issue

  While the investigation into the issue of images do not hit any fly/scrolling in a Webview (http://supportforums.blackberry.com/t5/Native-Development/Issue-With-Scrolling-Images-In-Webview/m-p...) I came across the question if a user buys my in-app purchase then removes the application and reinstall the in-app purchase did not work.

  First of all, in-app purchase is to remove the ads - it does that very well, but when the application is removed and reinstalled ads appear once more and I don't want to force consumers to pay twice, so I really need to get this fixed number as it is preventing me to release an update of my application.

  I'm working out of this example: http://supportforums.blackberry.com/t5/Native-Development/Sample-Removing-In-App-Ads/m-p/2783323/hig... and have used it to create buying app for my application.

  Here's my source, my main.qml of my application file code:

  import bb.cascades 1.0
  import bb.platform 1.0
  import com.sample.payment 1.0
  
  TabbedPane {
      id: tabbedPane
      property variant payment
  
      Menu.definition: MenuDefinition {
          id: appMenu
          actions: [
              ActionItem {
                  title: "About"
                  imageSource: "asset:///IMG/ic_info.png"
  
                  onTriggered: {
                      aboutSheet.open()
                  }
              },
              ActionItem {
                  title: "Contact Us"
                  imageSource: "asset:///IMG/ic_email.png"
  
                  onTriggered: {
                      emailInvocation.query.uri = "mailto:[email protected]?subject=Shopping For eBay App: Contact"
                      emailInvocation.query.updateQuery();
                  }
  
              },
              ActionItem {
                  id: upgradeAction
                  title: "Remove Ads"
                  imageSource: "asset:///IMG/ic_clear_list.png"
  
                  onTriggered: {
                      if (tabbedPane.payment) {
                          /* replace the values in quotes "" below with the values from
                           * your vendor account for this application's add-on. */
                          payment.mPaymentControl.pid = "{REMOVED}"
                          payment.mPaymentControl.sku = "{REMOVED}"
                          payment.mPaymentControl.name = "Remove Ads"
                          payment.mPaymentControl.metadata = "Purchasing this will remove the adverts!"
                          payment.mPaymentControl.getPrice(payment.mPaymentControl.pid, payment.mPaymentControl.sku);
                          payment.mPaymentControl.purchase(payment.mPaymentControl.pid, payment.mPaymentControl.sku, payment.mPaymentControl.name, payment.mPaymentControl.metadata)
                      }
                  }
                  attachedObjects: [
                      // Definition to hold the PaymentControl so it is only created when neccesary
                      ComponentDefinition {
                          id: paymentdef
                          Container {
                              id: payContainer
                              onCreationCompleted: {
                                  console.log("Payment Definition Created - Checking for Existing Purchases")
                                  paymentControl.getExisting(true);
                              }
  
                              property alias mPaymentControl: paymentControl
  
                              attachedObjects: [
                                  PaymentServiceControl {
                                      id: paymentControl
                                      property string pid
                                      property string sku
                                      property string name
                                      property string metadata
  
                                      // Play receipt animation on purchase response
  
                                      onPurchaseResponseSuccess: {
                                          cpp.saveValueFor("removedAds", "23");
                                          root.removedAds = 23;
                                          console.log("purchaseResponse - " + receiptString)
                                      }
                                      onInfoResponseError: {
                                          console.log("Purchase Error - " + errorCode + " - " + errorText)
                                      }
  
                                      onExistingPurchasesResponseSuccess: {
                                          if (receiptsString == "(No purchases)") {
                                              console.log("existing unable to find receipt")
                                          } else {
                                              console.log("existing receiptString - " + receiptsString)
                                              cpp.saveValueFor("removedAds", "23");
                                              root.removedAds = 23;
                                          }
                                          console.log("existingPurchaseResponse Success - " + receiptsString)
                                      }
                                  }
                              ]
                          }
                      }
                  ]
              },
              ActionItem {
                  title: "Share App"
                  imageSource: "asset:///IMG/ic_share.png"
  
                  onTriggered: {
                      invokeShare.trigger("bb.action.SHARE")
                  }
              },
              ActionItem {
                  title: "More Apps"
                  imageSource: "asset:///IMG/ic_buy.png"
  
                  onTriggered: {
                      invokebb.trigger("bb.action.OPEN")
                  }
              }
          ]
          attachedObjects: [
              Sheet {
                  id: aboutSheet
                  About {
                  }
              },
              Invocation {
                  id: invokeShare
                  query {
                      mimeType: "text/plain"
                      data: qsTr("Get your shopping done easily on your #BlackBerry10 with 'Shopping For eBay'; check it out in @BlackBerry World: http://appworld.blackberry.com/webstore/content/35964888/")
                      invokeActionId: "bb.action.SHARE"
                  }
              },
              Invocation {
                  id: invokebb
                  query {
                      mimeType: "text/html"
                      uri: "appworld://vendor/64825/"
                      invokeActionId: "bb.action.OPEN"
                  }
              },
              Invocation {
                  id: emailInvocation
                  query.mimeType: "text/plain"
                  query.invokeTargetId: "sys.pim.uib.email.hybridcomposer"
                  query.invokeActionId: "bb.action.SENDEMAIL"
                  onArmed: {
                      emailInvocation.trigger(emailInvocation.query.invokeActionId);
                  }
              }
          ]
      }
      showTabsOnActionBar: false
      Tab {
          title: qsTr("Home") + Retranslate.onLocaleOrLanguageChanged
          imageSource: "IMG/101.Home.png"
          NavigationPane {
              id: navigationPane0
              Page {
                  onCreationCompleted: {
                      root.removedAds = parseInt(cpp.getValueFor("removedAds", ""))
                      if (root.removedAds != 23) {
                          tabbedPane.payment = paymentdef.createObject(navigationPane0);
                      } else {
                          console.log("Not Creating Payment Definition, User has Already Paid To Remove Ads")
                      }
  
                  }
                  id: page1
                  //actionBar actions
  
                  //Title bar
  
                  Container {
                      id: root
                      property int removedAds
  
                      onRemovedAdsChanged: {
                          if (removedAds == 23) {
                              myAds.visible = false
                              myAds2.visible = false
                              appMenu.removeAction(upgradeAction)
                          }
                      }
                      Container {
                          id: myAds
                          horizontalAlignment: HorizontalAlignment.Center
                          layout: StackLayout {
  
                          }
                          MyAds {
                              horizontalAlignment: HorizontalAlignment.Center
                              topPadding: 15.0
                          }
                      }
                      Container {
  
                          layout: DockLayout {
  
                          }
                          // To enable scrolling in the WebView, it is put inside a ScrollView.
                          ScrollView {
                              id: scrollView
  
                              scrollViewProperties.overScrollEffectMode: OverScrollEffectMode.None
                              // We let the scroll view scroll in both x and y and enable zooming,
                              // max and min content zoom property is set in the WebViews onMinContentScaleChanged
                              // and onMaxContentScaleChanged signal handlers.
                              scrollViewProperties {
                                  scrollMode: ScrollMode.Vertical
                                  pinchToZoomEnabled: true
                              }
  
                              //Webview
  
                          } // ScrollView// A progress indicator that is used to show the loading status
                          Container {
                              bottomPadding: 25
                              horizontalAlignment: HorizontalAlignment.Center
                              verticalAlignment: VerticalAlignment.Bottom
  
                              ProgressIndicator {
                                  id: progressIndicator
                                  opacity: 0.0
                              }
                          }
                      }
                  } // End of container
              }
          }
      } //End of first tab
  } //End of tabbedPane
  

  Any help and advice in this regard would be greatly appricated.

  Thanks in advance!

  If you test using a sandbox past purchases account cannot be restored. Purchases made with a sandbox account did not get connected to the server, so if you try to restore (ex after you remove and then re - install the app even) then no purchase will be returned.

  You can test your rollback logic with purchases in the same session of the app: open the app, make a purchase, try a restore, all this without closing the application.

  The only other option would be to remove your account from the sandbox and try buying using real $$

• App purchase issue

  Hello

  one of our customers has very strange problem, he can't buy all of our apps. The weird part is this issue with our applications only, any other paid application has been purchased without any problems. No one is located in the United States and uses the carrier AT & T billing to purchase the app. I tried to contact the BlackBerry World team on the issue, but without success (no response in a few days). No matter who else had a similar problem with the purchase of apps from BBW or maybe have idea which team should I go? Thanks in advance

  Hi meego_man,

  This error comes from the carrier as this user tries to use the billing support.

  More information here: http://www.blackberry.com/btsc/KB33725

• iOS App rejection - In - App Purchase restore presentation

  I recently submitted my application to Apple for approval and that it was rejected, this time because the binary allows a feature restore "already purchased In - App Purchase products"; However, in iTunes Connect I have something setup in the In - App purchases, and the price of the app is set to release.

  Here is the message from apple:

  Restoration In - App purchase

  We found that your app includes a feature to restore already bought products from the In - App Purchase.

  It would be appropriate to revise your binary to remove this feature.

  For more information on In - App purchase 'types of purchasability', please visit the Guide of purchase of iTunes Connect App Setup

  
  

  
  

  Here are two screenshots, they sent me to the problem.

  
  

  

  

  
  

  You say that your application only has not any how in-app purchases implemented? If so, I would suggest to rebuild your application. The latest version of DPS 2015 included patch that removes the option 'Restore purchase' if the app does not purchase. See these bug fix release notes: https://helpx.adobe.com/digital-publishing-solution/release-note/bug-fix-release-notes.htm l

• "In App Purchase feature is not present in your binary."

  Our application was rejected twice now by iTunes.

  
  

  The first time we presented as an application multi-folio, with in-app purchases/non-consommables/0 layer $ price.  Told us that app in the purchase was not present in the binary file.

  
  

  " We found that, while you have submitted products In App Purchase for your application, the In App Purchase feature is not present in your binary.

  If you want to use to buy the App in your application, you will need to download a new binary that incorporates the in App purchase API to allow users to make a purchase

  Once you edit and resubmit your binary file, you also have to resubmit your in-App purchases for review, because they are in the State developer Action required. For each product in the IPA pointed out, please be sure to change the information in detail or to cancel the request to change the information in detail for App purchases using iTunes Connect. »

  We resubmitted as an application multi-folio with subscription iTunes, newsstand has enabled, with and without subscription in-app purchases / free. Yet once again, we have been rejected and said that app in the purchase was not present in the binary file.

  
  

  We try to understand what we're doing wrong and Apple was not much help.

  
  

  Bottom line, we want to offer our monthly magazine free of charge via the iOS app, just as we in the Google game store? Can anyone point us in the right direction?
  

  Don't implement everything in-app purchase in iTunes. Just post your public/free content in Folio Producer.

  Neil

• App magazine issues

  Hello

  We had a magazine in the Apple app store for about 7 months now. The magazine has been free, but we need to do a paid app. I went ahead and changed the settings in the newsstand on iTunes connect (for 99 cents). I have a few quick questions:

  1. I made a new application to submit to the app store with the DPS app Builder. I changed the type of subscription "paid". Then he asks the subscription products 'product ID' and 'duration '. I pulled our applications product ID from the In - App purchase screen in iTunes connect. Is this correct? In itunes connect there we like 'type' as a 'free '. In "paying subscription" will change once I submit to the new app and it gets approved? (I've already changed the info Bank with apple in order to manage this) I've included a few screenshots for reference.

  2. I exported the IPA file for test on my iPad. When I load this try out I wondered if it would begin to appear as a paid app. It loads all old issues of our magazine for FREE download. That should change now for 99 cents? Or because they were free they would be always free?

  3 subscriptions: when I open the application on the test API there is a button 'subscribe', but when I press nothing happens. Something else happened here or nothing was happening that it is just a test application?

  4. push notifications. I had trouble getting my push notifications works, but think that I figured them out now. Can I test this with the IPA file? I tried to send a notification by the producer of folio, but my test IPA did not. Does?

  Any help is appreciated.

  Thank you!

  

  You must also configure in-app purchases to your pages and add them to the subscription products in iTunes Connect to another existing folios will continue to be available for free. Then, you will need to republish them under retail sale slips. You can test if the subscription works in the sandbox by using your viewer developer by implementing of test user accounts in iTunes Connect. You will need to log out of the App store on the device with your regular account first. I think that push notifications do not work in the sandbox, but I'm not sure.

• Testing with sandbox and In - App purchases no longer works

  Hi, I'm currently testing in-app purchases...
  It worked well for a while, but now when I try to access the app on AppWorld with the contentID or the SKU

  I get this error message: "we are unable to connect to blackberry appworld please make sure that your device is connected to the wireless network and try again.

  I tried downloading a new project and is always the same.

  As for in-app purchases, I have an older version already installed that I could successfully make a purchase using the accounts of sandbox, but now I just can enumerate all purchases available from the server of the RIM, but when I try to 'buy' it returns an error: "Content not found, ID:XXXXX" or something like that.

  Anyone know what is happening?

  I was just notified that the payment of Sandbox server is currently down, which is the cause of these issues. I'll post to this Commission as soon as I hear that it is resolved.

• Are Android In - App purchase Descriptions to the Public?

  When configuring a single question in-app purchases in iTunes there is a reference field that identifies this issue reports on sales etc. and apparently not users at any time. I do not see a similar field in the game of Google but have yet to see the 'Description' field appears in the dialog of DPS.

  Anytime an app Android DPS reveals the field 'Description' of an in-app purchase or is it safe to use inside information?

  We show not just anywhere in the Android UI application. Game Google can show it in the purchase confirmation dialog, check here for if ensure it does not display before using it for more internal information.

  Neil

• Are all part of in-App purchases for a subscription i-Tunes?

  Hello

  We plan to introduce iTunes renewable subscriptions automatically.

  We publish monthly issues and special offers.

  We want the "normal Edition" to be part of the renewable subscription automatically. We sell also a 'special' which should be paid by everyone.

  How we accomplish this?

  The Apple Guide uses the following definition;

  Renewable subscriptions automatically

  "Renewable subscription automatically allow the user to buy of the dynamic content and update for a limited time."

  Subscription renewal automatically except if the user chooses, such as subscriptions to magazines. »

  If a customer buys a "renewable subscription automatically" 1 year 01/01/2014.

  Are all no consumables in-App purchases that are published during the period 01/01/2014 and the 31/12/2015 available for download? (point of sale)

  If we publish a special on 06/01/2014, how can we ensure that this special offer is not part of the subscription? How can force us everyone (even those with renewable subscriptions automatically) to pay for it in-app purchase.

  Any of you have experience with this case? I've asked Apple support, but their response was not clear.

  Thanks in advance.

  Erik Stuut

  Subscriptions are purely based on time. So yes, all questions between 01/01/2014 and the 31/12/2015 will be available for readers to download if they have a subscription that covers the range.

  We saw publishers to manage this is to set the date of publication of the special issue to something in the future. Then, it is not covered by an active subscription. The side effect is that the special issue will sort to the top of the list of the library.

  Neil

• Question about restoring In - App purchase

  We have this scenario and wanted to know the recommendations of Adobe.

  A customer has a multfolio app on the App Store with in-app purchases and active as well suscriptiones. Issues sold for several months. For some reason, he needs change the account of publication of DPS that it uses to publish folios.  He has already copied the current folios to the new DPS account and publishes them with the same folio product ID. He has not touched something else in the In - App purchases setting in iTunes Connect since there is nothing new to change on this section. Only, it creates a new application with the new DPS account ID. Subsequently, the .ipa installed fine and when you try to restore purchases, it displays an error (screenshot attached)...

  Have you ever been in this scenario before? That your suggestions about to compile one application with another account DPS without changing anything of the configuration of Apple?

  I really appreciate your recommendations

  Leo

  

  You must call the Gold support and ask for help.

  Neil

• In App Purchase and DPS restore settings

  

  Hi there, we have received this rejection from Apple after submitting our app and are a bit confusing. What this has to do with the submitted app or a decoration in DPS? Y at - it someone who can suggest how manage so we can submit our application successfully?

  This is probably because you have built non-renewable subscription in App purchases in iTunes Connect, when you should have built those renewable.

• I give up: try to change the application with In App Purchase

  This should be a simple process and a procedure.

  I have a soft retail de.99 in iTunes.

  I tried to change it for a free download, the first 7 pages of preview free app, with an In App Purchase de.99 to see the rest of the application.

  Followed all these instructions to the letter:

  http://www.Adobe.com/devnet/digitalpublishingsuite/articles/free-article-Preview.html

  iTunes rejects IPA because they do not see the IPA after page 7.

  I have the first 7 pages of the application defined as free in the producer of folio and the rest are marked as protected. Update the folio with the Public status and free.

  I guess the problem is that I have the app at the price of encore.99 in iTunes, but if I change it for free while waiting for approval from Apple it generates hundreds of downloads a day, and I end up having to buy another package of folio. Not exactly ideal.

  I spent the weeks with iTunes/Apple trying to get DPI approved. It should be such a simple process/procedure, but at this point, I'm ready to give up and let it run out my folio number and my professional subscription to expire.

  Unless someone has any experience with this problem and can offer specific advice / solutions?

  Thank you!

  You should publish the folio as Public & Retail, fix the price to $0,99 in iTunes in-app purchase. Because you have activated a free for the first 7 items preview, if a user moves on the folio, they see the pre-release 'free' or 'buy' option. They then click on 'free preview' and reading the first 7 items and when they hit article 8, that's when they are asked to buy if they want to continue reading the rest of the items.

• I can have renewable subscription automatically and not consumable In App Purchase in a single application?

  Hello world

  My application is simply live on the app store.  I used DPS Professional edition and I am able to create a Multifolio with itunes subscription app.  I put my subscription for 1 month and 1 year.  Now, I would like to publish any other questions for the nesstand to be free.

  It will approve by apple if I add no consumable In App Purchase and set the price to be free.

  In fact, I want my users to download free content, for back issues and buy the lateest those.

  Can what method I use to do this?

  In-app purchase is only for the issue of retail sales.

  You can publish free folios of dashboard DPS, which will automatically appear in app Live.

• Dates of publication and approval of in-app purchases

  We have a multi-folio with right and subscription itunes application. My questions are regarding the folio publication dates and approval of in-app purchases for unique folios.

  Let's say that you want the date of publication of your folio February to 04/02/2013. This date is important because we want to make sure that, regardless of how a subscription was purchased the first number is the same. If you buy one registered 04/02/2013 by Apple fulfillment or the system our company to purchase your first folio system should be the February issue.

  As far as I know, a folio must be published in order for Apple to review as part of the in-app purchase approval process. So what happens when you publish a folio on 04/02/2013, but it is not yet approved for an exemplary one in-app purchase? It is available for the subscribers of the law? Others see the folio but can not buy? And above all, is there a way to make the folio available to Apple for review before 04/02/2013 and not for the users of the application?

  Try to submit the app first purchase without publishing the folio. If Apple approves, as they have done with many customers, you don't need to worry about the time. Simply submit that in-app purchases in advance and publish folios when ready.

  If Apple does not approve, you might play a little game to publish the folio of detail as public and submitting the in-app purchase. When Apple approves, change the status of folio in private until it is ready to publish. Then re - publish the folio when ready.

• Advanced In - App purchases

  Hi, I've read several times that you can create up to 12 months of in-app purchases in Itunes Connect, how is that done exactly?

  For the moment, as I do is... One week before the date of sale, I create a Non-Consumble in-app purchase in Apple, the value of the folio public retail, which then allows me to see the app Dev and then do a screenshot of the purchased folio, download this to Apple so I can then submit purchase - 7 days for apple to approve what had been taken.

  The problem we are having is... every now and then someone load the official app and is notified that the next issue (currently awaiting approval from apple) is available, but they can't download it.

  In addition, while he sits there in the land of Apple, we still update the folio (tight).

  Thus, ideally, what I'd like is to create 12 months or so in-app purchases series is not allowed to sell but approved and then we simply change the status when necessary.

  What worries me is, if I create 12 months of empty folios Reatil Public people must be notified, if that is what is needed to create the screenshot in-app purchase.

  Thank you

  Andy

  Apple approves the in-app purchases based on the Description and screenshots. You can create breakthroughs in-App purchases and that you do not ready for sale to the date of publication.