How can I edit the redirect_uri in my SoundCloud apps dashboard? I go to http://soundcloud.com/you/apps but no edit button was found.
Editing is not possible at present, and so for now, you'll need to get in touch with the SoundCloud support team to edit this.
You can review this enhancement purposal on official Soundcloud API Github Repository , this was created on March 26, 2021 , where SoundCloud official team member accepted that it's a work in backlog and you can contact them to make updates to redirect URI.
To resolve this issue, you can send an email to SoundCloud at support#soundcloud.com to share the required changes and the target application for this change.
As of now, they are not providing this feature, due to the security reasons around the authentication connect flow.
Related
We are having trouble setting up Facebook Install Ads attribution via Branch.io. Currently, Branch.io dashboard shows we have installs via Facebook link, but Facebook ad cabinet shows 0 installs.
Our setup is
I've integrated branch.io for Flutter using this plugin https://pub.dev/packages/flutter_branch_sdk (Quick Links are working OK, see p.6)
I've setup Application on Facebook (developers.facebook.com) side and linked it to application in stores (AppStore and Google Play)
I've setup Facebook as Ad partner in Branch Dashboard > Partner Management, and then created Facebook link
I've created Ads in Facebook with aim Installs and used Branch link (all as per guides)
I've followed guides on Branch's docs regarding publishing - specified that we use IDFA in AppStore, all ticks as in guide, made sure we have AdSupport.framework in xCode project, added com.google.android.gms:play-services-ads:9+ in build.graddle, etc
I've exported some data from Branch Dashboard and IDFA/Android Id values were present (in Branch Dashboard > Exports > Custom Exports, as I understand, this exports Quick Links only, but still IDFA are there), this proves we are collecting these IDs.
Branch > Ads > Fraud dashboard is empty.
Branch SDK versions are 0.32.0 iOS and 5.0.1 Android
Regardless, Facebook doesn't see app Installs at all.
guides used:
https://help.branch.io/using-branch/docs/facebook-app-install-ads
https://help.branch.io/using-branch/docs/facebook-faq-and-advanced-options
https://help.branch.io/developers-hub/docs/apple-app-store
https://help.branch.io/developers-hub/docs/google-play
https://blog.branch.io/troubleshooting-facebook-install-ad-discrepancies/
What did I miss?
Thanks!
A Branchster Here -
Briefly explaining that SAN partners like Google AdWords/ Facebook integration is different from conventional non-SAN partners, where we send conversion data to SAN partners and they will claim the install/ Events according to their conversion logic and respond to us via API. Branch then analyses the data from all the partners and attributes the same Install/ Event based on last touch attribution logic. You will see less data on Branch dashboard as we show only attributed data for a SAN partner than the respective SAN dashboard. Please note Branch numbers is more accurate as we show the data as per cross-channel attribution.
Here are some troubleshooting you can do-
Please match both the attribution windows.
Please make sure you have synced the timezone on both Branch and Facebook
Please make sure you have signed the Facebook MMP or attribution data won't come.
I'll keep this post updated with general troubleshooting.
Issue is resolved.
Recreating Ad campaigns with exactly same settings resolved the issue.
Unfortunately both Branch and Facebook support were not helpful. :(
I have created a Branch link with some keys and values.
My app uses those values for multiple reasons. It works well when I open the link directly on my mobile browser or from a message.
But I want to use this link in a Facebook App download ad campaign. I have putted it as the ad deeplink. But when I install and then open the app via the ad thoses values are not sent.
Does anyone has managed to send keys/values via a branch link through a Facebook ad ?
Thanks
Matthias
Jackie from Branch here.
Branch supports deep-linked Facebook ads. We've created an FAQ page exactly for this and there are a few things you can check to diagnose the issue. You can go through them here (https://docs.branch.io/pages/deep-linked-ads/facebook-ads-faq/#troubleshooting-deep-linking). I'd also encourage you to use Facebook's tester tool, as mentioned in our FAQ doc.
Hope this helps. If you continue to experience issues, please feel free to reach out to us directly at integrations#branch.io. When you do, be sure to include your Branch app ID and the ad links you're using so that we can investigate further!
I'm looking at setting up an Instagram app so I can push content from my app directly to Instagram. I'm already doing this for Facebook, LinkedIn, and Twitter.
I know that Instagram is in the middle of moving to the Facebook Graph API, and it seems like there are several barriers to even start developing an app.
At the top of the Getting Started link there's a blurb stating that I need to undergo "Business Verification" to use the Instagram Graph API. Do I need to do this in order to use these endpoints in sandbox mode? (Edit: I believe this must be done in order to test the non-beta aspects of the API) In addition, the Content Publishing API seems to be locked down even further, requiring parternship with either Facebook or Instagram, and neither are accepting new applications.
Is there some way to test this in sandox mode without becoming a partner?
(Edit: Testing your app Suggests that I must do business validation in order to use the non-beta aspects, and there's no permission for publish_content, leading me to believe that I must be a business partner to even test this feature. Can anyone confirm?)
Januray 26, 2021
The Content Publishing beta has ended and all developers can now publish media on Instagram Professional accounts. Refer to the Content Publishing guide for usage details.
https://developers.facebook.com/docs/instagram-api/guides/content-publishing
I am trying to connect Social Connected to Facebook using Sitecore 8's (rev 5) Social Connected functionality (we are unable to use Komfo for budget reasons) however i've had a few issues. I was following this walkthrough from the Sitecore documentation site.
I was getting this error when trying to connect a Facebook account:
"Invalid Scopes: read_stream. This message is only shown to developers. Users of your app will ignore these permissions if present.
Please read the documentation for valid permissions at: https://developers.facebook.com/docs/facebook-login/permissions"
So I went ahead and did some reading and found this Stack Overflow question
which from the information there I was able to find that the particular permissions that Sitecore is asking Facebook for are deprecated.
From there I changed the permission from publish_stream to publish_actions and was able to give Sitecore the permissions it needed in Facebook. The problem is that Sitecore wanted this to be done in the browser window it provided, and so it did not acknowledge that the permissions were set in Facebook, even though they were.
I then tried to manually add a social media account from a template, hoping to input the data it would need manually now that it had the appropriate permissions. However after doing this Sitecore then started to throw an error when adding other social media accounts:
"The Social Connected Module is not configured.
There are no social networks available with applications that you can use to create an account."
Social connected is in fact configured, and before making these changes I was still able to add other social media accounts. Recreating the Applications solves this issue but puts me back at square one.
Any ideas on how we can rectify these issues would be greatly appreciated.
I managed to get around this issue. First, in the content editor, I created a Facebook application under System/Social/Applications. Then, I created a social media account under System/Social/Accounts for LinkedIn and then duplicated it, changing the configuration to suit Facebook.
Once I did this I was able to post text posts to Facebook and Twitter. I was not able to get image posts working, and by this time, we abandoned the idea.
It's worth noting that Sitecore continued to push us toward Komfo. It's pricey and is essentially an iframe placed in the Sitecore UI with limited functionality. There are other tools out there that will give you similar analytics features for a fraction of the price.
It's also worth noting that the social connected functionality in Sitecore 8.1 appears to ask Facebook for the correct permissions, so you wont have this issue. I cannot vouch for its functionality in terms of actually posting as I haven't fully tested it.
Fortunately, Facebook permissions are only string and you can easily modify it using reverse engineering. It was done for Sitecore 7 version, but I think same approach will work for Sitecore 8.
Also, you are able to create a ticket in Sitecore support and they will provide you hotfix for this issue.
Here is the notification I just received:
App, is currently using the following deprecated features:
Non-threaded comments. Please see the developer roadmap for more details about this change.
I looked all over the API and the developer roadmap and the settings but found no way to fix this issue. How do I fix this?
My hunch would be that they send out alerts based on the permissions your app uses - my app doesn't interact with any "comments" connections in the graph, but it does have the "publish_stream" and "manage_pages" permissions.
If someone knows otherwise please advise...
I have received the same notification for one of my apps. My app definitely does not read or create comments on Facebook posts or objects (Facebook rolled out the threaded comments Feature in April). Thus Facebook's message is not relevant to every app they send it to.
The change should only affect apps which read or publish comments.
Here is the link to the API documentation about comments:
http://developers.facebook.com/docs/reference/api/Comment/
Look at the settings page, in the "Migrations" section. Enable "July 2013 Breaking Changes" and your notification should have a green sign notifying: Your app, appname, is now compliant with the July 2013 Breaking Changes migration. No further action is required.
Be sure to read the complete roadmap at https://developers.facebook.com/roadmap/.
I have got the following message too:
MyApp, is currently using the following deprecated features:
The 'page_id' field in the checkin FQL table. Please use 'target_id' instead.
The 'version' field in the group FQL Table and on the Graph API.
Non-threaded comments. Please see the developer roadmap for more details about this change.
I am sure that in my case the warning derives from my Graph API Explorer and
my Django test code.
That means that Facebook logs every request sent by your App and send you a warning even if you used deprecated features only once.
Check it out