I am trying to use facebook ios sdk but when I run the Hackbook example it gives me the error message "Invalid or missing URL scheme. You cannot run the app unti you set up a valid URL scheme in your .plist" Where do I make the changes for this?
Since one of the answers mentioned it, I will say that I have already modified the plist to have fb[my_app_id] in the URLSchemes.
This tutorial walks you through the process step by step, search for "Modify the app property list file".
I figured it out. There was another instance in the code where the ID needed to be replaced. What's odd is that it's not specifically called out as far as I can tell. I did a search for it.
you have to add like this
100% works and solved crash
Related
I'm trying to get my swift Mac app to launch at login using the method described in this page: https://theswiftdev.com/how-to-launch-a-macos-app-at-login/
However, I keep getting the following errors as soon as I call SMLoginItemSetEnabled:
Could not locate login item com.domain.LauncherApplication in the caller's bundle
Could not enable login item: com.domain.LauncherApplication: 3: No such process
I checked that the launcher app ID is correct multiple times, I tried changing it and changing its version number. I even tried cleaning the project and moving the base app to /Applications but I always get these error messages.
Any idea what the problem might be? (Notice the solution must not require me to disable App Sandboxing)
OK, I found the problem but it took a long time since it was so sneaky: In the Copy File Build Phase section I entered "Contents/Library/LoginItem" as the subpath instead of "Contents/Library/LoginItems" (notice the 's' in the end - can't believe I missed it). So thank you #vadian! You were absolutely right.
For a project that I'm working on that is in Alpha right now, I used to use an invocation ''talk to XXX''. Now that I want to deploy the Action to Beta, I want to change the invocation name/phrase as well. So I changed it to ''talk to YYY'', which is the suggested input field in the simulator as well. But when I want to test this in the simulator, I get the following error message:
Invocation Error:
You cannot use standard Google Assistant features in the Simulator. If you want to try them, use Google Assistant on your phone or other compatible devices.
For some reason, if I ignore the suggested input chip (which says ''talk to YYY'') and type in ''talk to XXX'' (the old invocation phrase) everything still works though. Seems that I'm missing something and Google support can't answer me, does someone know what I can do to successfully deploy to Beta?
When I get that message, it's usually a problem with the Console. A refresh of the page—and sometimes a simple retry—usually does the trick.
You could also try "Change Version" to make sure you're pointed to "Draft".
I am using Appium Desktop app. After adding all the capabilities. When I Start session, I got an error "An unknown server-side error occurred while processing the command. Original error: You must include a platformName capability"
Screenshot
Like Pankaj Mishra say, it is really.
The APPIUM Desktop UI have some bugs and the only way to solve this problem it's typing the capibilities directly in the fields and never copy paste or edit like a JSON format.
Screenshot of the correct way to do the configuration
APPIUM Desktop UI have some bugs as a result you get this error even if the capabilties are present.
You can refer Here to avoid above issue.
Based on your screenshot, you made a spelling mistake:
flatformName: android
flatformVersion: 8.1
You need to fix f to p and it will work perfectly for you!
Make sure you enter "platformName". Not "platformName ". Can you see the difference? Second one has a hidden space which could often happen when you copy-past the capability name.
make you've write correct words "platformName:" and check your json representation.
I'm developing an hybrid app and I want to skip the passcode screen after having logged.
I've tried following a post about Kapsel-Logon where it is explained how to implement it, but it doesn't work for me. I don't know if the latest release makes changes null.
The file I tried to modify is:
C:\KapselSDK\plugins\logon\www\common\modules\LogonController.js
Can you help me or suggest where I wrong or what can I do/look?
yes the file that you need to change is the LogonController.js
You can find here what exactly you need to do in order to get rid the passcode screen.
Good luck!
I have downloaded the source project from
sourcecode.
I came across many issues over there, then I changed the source header path then changed the compiler version in the project settings, then all those were solved, now there is no errors, it runs, when I click FBLoginButton ,Facebook Login Dialog appeared but it looks empty,
I dont know why, The app key and app secret key were placed correctly.
I tried with device,if there would probm with simulator, still looks same.
what Im doing wrong, I had searched a lot, not found any solution, any ideas pls tell me
I have the same problem.
I have opened a bug here : https://developers.facebook.com/bugs/279606225487338
You can also vote for it, so that FB may take a look at it. Let's hope they solve it.
We had two apps in the app store which used this old api of facebook for login and they also g=have stopped working... So most probably Facebook has stopped support for this but I couldn't fond anything official. I guess we will have to incorporate the new Api.. :/ If I find something I will post here...