I've uploaded an app to Huawei AG but rejected by a message like
"Dear developer, the functions in your App are unavailable and we can
not edit content in it after we logged in successfully, please modify
it."
My app is already available on the Apple App Store and Google Play store and working properly so I don't think that it is unsuitable. I've check Huawei's review guideline but couldn't find any solution.
Does anyone know why this is happening?
Your app has been rejected, and the rejection reason is "Dear developer, the functions in your app are unavailable and we cannot edit content in it after we logged in successfully, please modify it." Check whether your app has the problem. You are advised to test the relevant functions.
Related
I can't get my app to be reviewed through the Facebook API.
The app is purely a facebook messenger bot, and the app type is "business".
I have configured the specific permissions I need, however I recieve an error that states "You do not have any platforms eligible for review. Please configure a platform on your Settings page."
I also cannot add my app domain in the basic settings, as whenever I press save changes, the url does not save and disappears.
Additionally there is no option to make my app live.
Any advice?
The error message
I am leaving this answer in the event someone else needs it. It was an answer suggested by Facebook support when I encountered the same problem.
Go into App Settings and add a platform "Website"
Just add your website URL.
If the requested permission is just Messenger based then the website will not be accessed or tested.
Last year I developed a chatbot with Microsoft Bot Framework that I integrated in the Facebook Messenger of a page. Everything worked fine until 16th of December (last successful log). The page is not used by a lot of people therefore the application might have worked also longer than that.
Today I tried to use the chatbot again and I did not get any response. In the Logs I just found the error message "Operation returned an invalid status code 'Forbidden`".
After a bit of Debugging I found out that the problem is sending messages back to the Facebook Messenger.
context.SendActivityAsync(...)
I did not change any configuration within my Azure Bot Channel registration recently. I am aware of the privacy changes within the Facebook API, but as I already struggle with sending a simple text response like "Hi" I assume that cannot be the problem. Also the permission scheme has changed for Facebook apps. I have the permission for "pages_messaging". Do I need another permission now? Or did I miss another change in the Facebook API?
Technical Details:
Facebook API Version v6 (tried also v9 but no change in behavior)
Chatbot based on .Net Core 2.1
Bot Builder SDK v 4.11
Any hints what I did wrong or where I can look for further information is much appreciated.
Edit: I tried to add a new page to my Facebook App and get following message:
There is a hint that a permission is missing, but I cannot find out which one I require. As I only send responses to FAQ's and if required handover to the customer service inbox I just requested the "pages_messaging" permission. Do I require any other permission now?
I found the problem. For everyone that might have the same problem:
In our case the administrator that added the Facebook pages to the application was removed from the admin permission list of the pages. After re-adding the admin permissions for the pages the bot started working again.
I'm uploading a new build of my iOS app and as always, I was going to check the IDFA options but I can't find them anywhere! Did something change?
It seems after requirement that apps use IDFA must ask users permission, Apple doesn't ask developers to select whether app use IDFA in App Store connect anymore.
So just submit app and don't care about it. I have submited an app successfully.
I just released my app on google play. When the app tries to login to google game service, I get an pop saying "Failed to sign in. Please check your network connection and try again". I have been able to login during the development of the app.
In google developer console, I have linked both the debug and release version of my app.
One thing that might be the problem is that I published the app before the game service (which is not recommended by google). Is this the problem? How do I fix this? How can I debug this?
As referred with this link and from this forum, if the phone has the wrong time/date you will encounter this error. You may also check the answer in Failed to sign in. Please check your network connection and try again. I have moved app id and leaderboard id from strings.xml to ids.xml in values folder. I have deleted all client ids and add again client ids for debug keystore and release keystore. Hope this helps!
I had a working hangout app until yesterday - but now now I can no longer launch the app in the developer sandbox.
In the process of diagnosing the problem I have tracked back to simply trying to launch one of the Google sample apps (https://plushangoutstarter.appspot.com/static/simpleHangoutApp.xml) in the developer sandbox.
This fails in the same way as my app: the hangout says loading app along with a lovely animation but never loads.
I have tried this from different Google accounts and OS's but the problem is the same whatever.
The js console shows the following error:
Uncaught SyntaxError: Unexpected token < login.corp.google.com/request?s=oz-autopush-full.plus.corp.google.com:443/u….google.com/js/api.js&maxAge=1200&authLevel=2000000&rpMode=v2&keyIds=Do0:2
Interestingly I can launch the hangout apps (mine and the sample ones) outside the sandbox. For example, https://plus.google.com/hangouts/_/16fae425e33645b520c4b14f71adbdbba843f00d
To me it seems as if Google has deployed a breaking change but I can't believe that there would be no activity on twitter or the google plus developer group if they had.
My questions are:
1) Can anyone launch an app in the developer sandbox
2) If not, anyone got any idea what the problem is.
Thanks in advance for any help. As usual in these situations, I was planning on demoing my app to my colleagues in a couple of days to show them how cool the hangouts api is :(
Neil
There was a problem on Google's side over the weekend and has now been corrected.