There appears to be a bug when clicking the inner close button of the ShareDialog, resolving the promise with {postId: null} instead of {isCancelled: true}
This only happens when selecting the inner close button. The outer button works fine.
Multiple button example:
The links are successfully shared though but do not return a postId(always null). Currently I can't determine whether someone closed the dialog or made a successful share...
To make matters stranger, everything works fine - closing the dialog with either button and also returning a valid postId - when using the LoginManager with the "publish_actions" permission and loading the ShareDialog afterwards.
However, Facebook deems the "publish_actions" permission unnecessary when using the ShareDialog.
The problem occurs in my own app and also the sample app found here: https://github.com/facebook/react-native-fbsdk/tree/master/sample/HelloFacebook
Other details:
react-native 0.45.0
react-native-fbsdk 0.6.0
android facebook sdk 4.22.1
problems occurs on emulator and physical device
Looks like this behaviour is part of the android sdk and not a bug. The onSuccess callback is called on closing the share dialog(why I don't know) and also a successful share.
https://developers.facebook.com/bugs/890116221030179/
So if you need to determine whether a post has been shared it looks like the "publish_actions" permission is needed.
Related
I have a Vue3 app which is giving me multiple errors only when I mount a specific component within my generic modal component. On desktop across browsers I get zero errors and everything works as expected. On iOS (using desktop Safari connected locally to capture console logs) it shows the log below, along with a few other "Maximum recursive updates..." from other components (which have nothing to do with the modal or it's inner template).
I've checked every single component that is listed in the error below ("at~") and every other component that is used in that modal template (it's only one template that breaks) and NONE of them are using a mounted hook, so the "Unhandled exception during mounted hook" doesn't make any sense.
I know this is not much to go on, but has anyone else seen this recursive error happen only in certain components and only in iOS before?
In addition to the above, I've double checked all logic for any recursive issues and have found none. And, if there really were some, I would assume they would show up on desktop as well, not only on iOS.
Pretty stumped here, friends.
Xcode has the ability to live record UI tests, as demonstrated by this YouTube video - the user clicks buttons on the Simulator and the code appears in test.
However, when I do the same action on this freshly pushed to GitHub Xcode project nothing code appears. What is my missing ingredient?
This is the screen I see.
and this is a recording of what it looks like live. What am I missing?
EDIT - tried an entirely new user account, different project, button didn't appear at all. Twich video here, I must be missing something...
I've been able to distinguish between the live build and the test build on my Android app. Everything works perfectly on the test version. I can see the live events and when I go and see the number of clicks for an event, that gets updated too. However, on the live build of my app, I can see the live events but the number of clicks is not being updated. All the events still show empty analytics. What could be wrong?
Amruta from Branch.io here:
Based on your description it looks like your App is still using the test key. If your App has both the Live and Test key added to the Manifest, and you have the debug mode enabled, your App will continue using the Test key. You should make sure that your App is using the Live key.
You can ensure that your app is using the Live key by using a Branch link from the Live version of your App. On clicking on the link, the link parameters received in the callback should have the parameter '+clicked_branch_link: true'.
If the parameter 'clicked_branch_link' is set to false it means that your App is still using the test key.
If you still continue to face issues, I would suggest writing to integrations#branch.io and they can help you resolve any issues you are facing.
After creating a branch link and using it to install the app, then repeatedly tapping on the link again - that causes the app to re-open I am expecting to see events (install, open, referred session) in Dashboard > LiveView but there are no events recorded there at all.
Is there something I am missing that I need to configure to see events in LiveView?
The marketing view also only shows clicks and nothing against Installs or Re-opens?
Alex from Branch.io here: what you are doing should work as you describe, so there is probably some sort of configuration issue. Some things you can check:
Are you using the same Branch key inside your app as was used to generate the link(s)?
Try enabling debug mode to make sure the system isn't throwing out your events as fraudulent
The Marketing view sometimes has a delay, but the Live View should be at most 10-15 seconds behind. Are you seeing new data in the Clicks tab, but just not the Events tab?
Feel free to submit a ticket with additional details, so that we can help debug from the back end!
I want to add a link from my app to another of my apps on the appstore.
Question How to link to apps on the app store showed that the itunes.apple.com link was,until recently, the normal way to go. I've tried this and everything is fine. The problem begins when I disgard this and use Apple's new recommendation of using appstore.com. I use the following line of code:
[UIApplication sharedApplication] openURL:[NSURL URLWithString:#http://appstore.com/myappname"]];
The first time I call this from my app it works well. You see it jump through Safari and move onto the appstore where it displays my app.
At this point if you look back into Safari you will notice a new blank tab labelled Favourites has been created.
If I go back to my app and perform the same action to link to the appstore again I'm prompted with one of the two popup boxes:
"Open this page in "App Store"? [Cancel] or [Open].
or
"Cannot Open Page. Safari cannot open the page because the address is invalid" [OK]
I've found that manually deleting the blank tab in Safari will allow the link to work properly but this behaviour isn't what I want my users to see- and I wouldn't be expecting them to delete the blank tabs from Safari.
Any advice on stopping this behaviour whilst following Apple's new rules greatly appreciated.
A simple and clean solution is to present an instance of SKStoreProductViewController inside your app (modally) to display information on the products you are interested in. The user can interact with it as a small view on the App Store and you can simply dismiss it when done.