I recently upgraded to Branch Unity SDK version 0.6.5 from https://github.com/BranchMetrics/unity-branch-deep-linking-attribution/releases and facing session initialization issues. which was working fine before.
On Android, if when the app opens from a deep link the callback is giving error: "Session initialization already happened. set intent extra, "branch_force_new_session", to true."
I need to retrieve link metadata to display the desired UI. So, I need the link properties.
Anybody faced this before? any fix?
Seams like you are initialising the SDK twice.
Are you initialising it in your onStart() and then trying to read the data with some other function that uses the initSession() method? If so, remove the first initialisation.
If you still have the issue, kindly share your implementation of initialisation and reading of link deeplink data from the link.
Related
I'm getting this error when opening VS Code. Does anyone know what it means? I've done some research but didn't get any relevant information :(
I've tried creating a workflow to see if the error disappeared, but it didn't.
It seems that react native is asking for a workspace to start but is it asking that in the first place? Can I disable react native from running when opening VS Code?
The folder opened when the screenshot above was taken was the folder it opens by default, I believe it's the mac "home" personal folder, and I have a folder called "git" inside of it, with all projects.
Given the date of this posting (2023-02-07), you're probably on version 1.10.0 of the extension. This sounds like this bug report in the microsoft/vscode-react-native GitHub repo: [Bug] Extension activating when it shouldn't #1891.
A fix is coming in version 1.10.1.
But it is taking some time and has not been release yet at the time of this writing 2023-01-31:
we're facing some problems in the last release process, recently we're waiting for new publishing PAT access to republish 1.10.1 again, maybe it will publish on marketplace on next week. We have nightly version for extension in marketplace as well, maybe you can use it now.
For now, you can try installing the nightly version.
Also, note from the extension's readme documentation:
Before going any further make sure that you:
have a working React Native environment.
have the emulator utility available in your PATH if you're developing Android applications.
[...]
Got it, this annoying log came from React Native Tools extension. They specify the requirements in the docs:
In my case, I don't have a specific React Native environment or the emulator PATH is not right.
I have a react-native app. I recently moved to react-native version 0.61.5 for which I took the long route of creating a new react-native app and porting my code over to avoid any linking issues since new version used PODFILE as the default linking mechanism. Ever since I moved to version 0.61.5, I don't get the correct location of code in error logs. I think this is mainly happening when the code is running in asynchronous fashion which most of the code is. For e.g., look at below screenshot:
It is reporting that it is not able to call map on some array which is apparently undefined but the place where the error is reported is completely incorrect. I have no such file in my codebase and it is probably pointing to some file in some react-native package.
I am using Sentry #sentry/react-native": "^1.1.0". I don't think Sentry can cause issue with the sourcemaps reported during development.
I am not sure how to debug this problem. This problem is causing a lot of issues in debugging any errors as I have to manually figure out where the error happened. Please let me know if you have any tips on how to fix this problem.
We have a custom authorization plugin for OSX, written using this as our base:
https://github.com/skycocker/NameAndPassword
and referencing the official documentation where needed:
https://developer.apple.com/documentation/security/authorization_plug-ins/using_authorization_plug-ins
The plugin was working perfectly, until the Mojave release. With Mojave, our auth plugin UI does not draw and we only see the circular login arrow button. The only way to login is to ssh into the machine, uninstall our auth plugin and re-enable to default OSX login mechanism.
We added additional logging and found that the plugin is indeed being loaded and runs normally. It's just the UI that is not displaying anymore. My guess is that they have changed some requirements for custom auth plugins but have not updated the documentation.
Does anyone have any ideas as to why the UI might not be displaying in Mojave?
EDIT:
Some more information. We have found that we are able to tab through the controls that are part of our plugin. This implies that the controls are actually there, but are either off screen or maybe just not being drawn? Very strange indeed...
EDIT 2:
I tried building the NameAndPassword sample, and it displays fine in Mojave. This sample used a .nib for the interface, which I cannot edit in the recent version of xcode. So, I tried recreating the interface as a .xib and surprisingly, the UI for NameAndPassword is now gone as well!
So, there is perhaps something happening behind the scenes when the .xib file is compiled which is causing the UI to not be drawn, which is NOT happening with a .nib based interface.
Do you have this flag enabled : self.window?.canBecomeVisibleWithoutLogin = true
I am facing a strange compiler error in upload-sym file which is used for firebase crash reporting platform. I am using the latest update from FirebaseCrash 2.0.0.
Please check out this photo in xCode 8.3.2:
I tried cleaning the build path, clean, build,research online for some kind of solution but it seems to be I'm the first one who has faced it.
Im using x-code 3.2.4 and I'm using the ios4.1 sdk.
I'm getting the following error when I try to call "ExtAudioFileOpenURL" from the audio toolbox.
Detected an attempt to call a symbol
in system libraries that is not
present on the iPhone:
_Unwind_Resume called from function _ZN15ID3ParserHandleC2EPvPFlS0_mmmPS0_PmE
in image AudioToolbox.
Why is this happening and how can I fix it?
Thanks,
db.
EDIT
In addition when running on a 4.1 device I get this error "error: 805297555"
What the hell?
The exact line of code causing the problem is this.
// Open an audio file and associate it with the extended audio file object.
OSStatus result= ExtAudioFileOpenURL (sourceURLArray[audioFile], &audioFileObject);
It's straight out of a sample code project. That sample code project runs fine.
I don't understand why if I start a new project with the same code I get errors.
This means that ExtAudioFileOpenURL is an unsupported API on the iPhone. ExtAudioFileOpenURL probably makes use of some exception handling API that is not available on the iPhone, which is why you are seing this sympton of the underlying error.
What I had to do in the end was completely uninstall the developer tools from my machine.
Then download the latest versions of xcode & ios SDK.
Everything works ok now.
Sadly I still don't exactly know what the problem was but at least things are running.