I was using an app with graph api permission of ChannelMessage.Read.All.
Since 4 days (4th of july) this does not work anylonger although it was working fine the last several months.
The documentation states now, that app permission is not supported anymore.
https://learn.microsoft.com/en-us/graph/api/channel-list-messages?view=graph-rest-beta&tabs=http
What's the reason why this has been removed? Any plans to get this back?
It is not practical to use delegated permission.
please help
thx
stefan
Related
I am getting this message in my AdMob account.
IAB TCF v2.0 errors detected We've detected an issue on your IAB TC string on one or more of your sites or apps. These errors may affect your ability to serve ads to European users. A detailed report is available for you on the EU user consent page.
And as I found error 3.3 indicates that The TC string last updated date was more than 13 months ago. and the suggested action is CMP should delete the old TC string and reobtain consent.
And I am using Funding Choices as a CMP, so how can I resolve this issue?
Do I need to do any changes to the app for it?
Please guide me on the solution if anyone has solution of this issue, it will be very helpful to me
Thanks
according to that Google group if you are using UMP SDK, and you probably are as you're using Funding Choices like me, it should be handled by the SDK itself. So nothing to worry about, if the error persist, meaning it present itself in several different days, than I fear the only way is to open a ticket with Google Admob.
Where to find complete list of iOS app permissions?
For android you may find a complete list of normal and dangerous permissions, which apps could use: https://developer.android.com/guide/topics/permissions/requesting.html
Of course I know the "dangerous" permissions of iOS, they are displayed in settings>privacy. But Im also interested in the normal settings which can not be influenced by user.
I think for developers there should be a list like that for android. Or ist the system working completely another way? So where could I learn about this?
Why am I asking? For my degree Im researching whether users now which data is collected in smart mobile devices. Therefore I need a reference.
This may be useful:
https://www.apple.com/business/docs/iOS_Security_Guide.pdf
Relevant post:
Complete list of iOS app permissions
The info.plist is where you can add keys for permissions when writing your iOS app. Here's the documentation for that:
https://developer.apple.com/library/content/documentation/General/Reference/InfoPlistKeyReference/Introduction/Introduction.html
I run my own VPS in Amsterdam where I have a MySQL database that is being populated and maintained using ASP.NET. It's a Windows Server.
I use this API for four of my existing Android apps (published and working) with a few thousand users who never had any issues connecting to the API through those apps. Recently I finished one of the apps on the iOS platform and it got rejected because Apple couldn't get it to load any content, or it would get stuck on loading without ever returning anything (after we implemented a loading progress animation). After a lot of messaging between me and Apple's review team, they ended up accepting my app to be passed through review even though they never got it to work (or so I believe, they just said they would re-review it and it suddenly got approved after 7 rejects). None of my friends, family or users ever experienced any issues like this on either Android or iOS.
A good friend of mine who did most of the work on the API is also from the USA, which makes me doubt it's a location problem.
I must note that pretty much 99.99% of my users are Dutch and all my projects are build for Dutch users.
Does anyone have experience or ideas in this field? I'm about to publish an update for the already published app and I'm afraid they will reject it because of the same issue.
The exact message I got at first was:
Specifically, upon launch we found that the app failed to load any content.
Changing the API calls to be over HTTPS seems to have fixed the issue, Apple now has access to my API through all my apps.
I have an app through which user can share on twitter. Everything was going great few days ago but suddenly, I started receiving permission errors. I checked my permissions but surprisingly, I got this:
Permissions are also set as read write but still I am getting error on sharing.
I don't know what is wrong. Any suggestions?
This has happened to a number of developers - see https://twitter.com/TwitterDev/status/473547632669782016
If your application lost write access this week-end and you believe this is an error, please fill https://t.co/jUQPuVHhyo (3rd option).
I've been looking for a good iOS Facebook API/SDK Wrapper, can't find any.
I need to be able to (with a few lines of code, not the insanely needed by Facebook's API):
Login user
Logout user
Get user's likes
Invite Friend to app
Maybe post to user's wall (this has been causing problems to other apps so not sure will actually implement)
Get user's friends
Get user's basic info (e-mail, name, etc.)
Is there any wrapper simplifying the absurd vanilla API?
https://developers.facebook.com/docs/reference/apis/
This should help and it is Facebook's official api.
Here's the documentation: https://developers.facebook.com/docs/ios/
You might be able to use portions of ShareKit for this (be sure to abide by their license): https://github.com/ShareKit/ShareKit/tree/master/Classes/ShareKit/Sharers/Services/Facebook
This doesn't do everything you asked, but it's a (clean) starting point at least: https://github.com/mobitar/Zuckerkit
This does a bit more, but hasn't been updated in a year: https://github.com/sinnerschrader-mobile/S2M-Facebook-iOS
I found this lib: https://github.com/lucascorrea/SCFacebook
It seems to use a not that outdated version of the iOS SDK (3.18 vs. current 3.21), is available on cocoapods and seems to cover many of your required API features.
I haven't used the lib my self, but i am considering it next time i have to develop an iOS App which needs to connect to facebook.