I have download the Whole code from JIRA Mobile connect's home site but
I have facing this issue while install the JIRA Mobile connect,All the things is perfect but in My project i have one JMCViewController.xib and it contain one scrollview and the class assign to that scrollview is JMCScrollViewContainer and that is missing so How to find that class, I have tried all the things but not get success so can any one solve this problem? Please help
Thanx in Advance for any Help Any Suggestion,
These classes were added recently so you will need to manually add them.
You can get them from here https://bitbucket.org/atlassian/jiraconnect-ios/src/0f2c90244acd/JIRAConnect/JMCClasses/Core/views
Related
i have been using an url launch that open sygic and drives to coordinates n my website.
It looks like this: com.sygic.aura://coordinate|15.06591|47.73341|drive
After the last Sygic update this url launch does not work anymore, it fires up Sygic but no route is calculated any longer.
Does anybody have som ideas to overcome this?
Is there anyone else that hava this problem and found a solution for it?
This is what i tested with iPad Air 12.5.3, Sygic Version 20.4.5
All of Sygics custom url: https://www.sygic.com/developers/professional-navigation-sdk/ios/custom-url
I contacted the Sygic Support. Here is their answer:
Thank you for contacting Sygic.
We apologize for the inconvenience. You're using the legacy format which is no longer supported in the latest release. Instead of this format, universal links can be used.
For your use case, you can use:
https://go.sygic.com/directions?to=latitude,longitude
I am trying to create an Adaptation Project for SAP Fiori elements. But when I am trying to get the project from System it is showing me an error. shown in screenshot.
I am following Tutorial mentioned in link Adaptaion Project by Jessica Merz
I am not sure why is this coming. I tried searching many blogs without any luck,
is it issue of some Authorization or missing some profile ?
kindly let me know if someone faced same issue as me.
Yes, your users is missing required authorization objects.
S_DEVELOP
S_ICF_ADM
S_TCODE
S_TRANSPRT
S_CTS_ADMI
S_CTS_SADM
I am currently using LoginKit github.com/IcaliaLabs/LoginKit to set up my login and signup screens. I am confused with how to add to my project. (I already have the pods installed and working on the XCWorkspace). If somebody could help me implement this that would be very helpful. If you need screenshots of my project let me know.
everyone. Today I encounter the following message in my Windows Phone App:
Success
SECURITY WARNING: Please treat the URL above as you would your password and do not share it with anyone.
This happens when my users Login through the Web Browser Control, which get the Login URL from the GetLoginUrl method from the Facebook SDK for .net. This problem is not only happening in my Apps, I've seen users from other Apps having the same problem.
Anyone found a solution to this?
I'm running this SDK in my PictureWeather (Windows Phone 7 & Windows Phone 8) and Picture2Cams (Windows Phone 8) Apps.
Had the same problem. In my app I changed this line:
parameters["redirect_uri"] = "https://www.facebook.com/connect/login_success.html";
To this line:
parameters["redirect_uri"] = "https://m.facebook.com/connect/login_success.html";
And it works now.
Had the same problem on our WP8 app using the Facebook SDK for Windows Phone (http://facebooksdk.net/docs/phone/) and the indicated solution with changing the redirect URL also worked for us.
Thanks for submitting this solution.
I ran into this problem, myself, and did a bit of digging to get to the root of the issue. The problem seems to spring from some unknown (to me, anyway) change on Facebook's side, where previously the authentication response URL was in the form
https://www.facebook.com/connect/login_success.html#access_token= ...
for some reason it now comes back from the login flow as
https://www.facebook.com/connect/login_success.html#?access_token= ...
The code in FacebookSDK.NET does a comparison in line 104 of LoginPage.xaml.cs with a simple Uri equality test
if (e.Uri == WebAuthenticationBroker.EndUri)
which fails to return true when the question mark appears in the middle. I expect Facebook will correct this on their end just because too much stuff breaks, but in the meantime a pretty clean fix is to get the FacebookClient sources from GIT instead of NuGet and change the comparison to this
UriBuilder clean = new UriBuilder(e.Uri);
clean.Query = "";
if (clean.Uri == WebAuthenticationBroker.EndUri)
The code will then run just fine, but this is seems ultimately to be Facebook's bug when checking the documentation on their developer site.
I hope this helps some others, I signed up for Stackoverflow just to make this post. :)
Use latest facebook sdk for windows phone. This issue got resolved in latest sdk. I am using Facebook.Client 0.8.2-alpha and its working great. I followed http://nuget.org/packages/Facebook.Client and http://facebooksdk.net/docs/phone/controls/login-ui-control
I guess the only way he did this was by downloading both projects from their official Github (Facebook and Facebook.Client) and reference them in your app instead of using the DLL that you can get from Nuget.
With both projects in hand, you can change this parameters on the Facebook.Client Project in the file FacebookSessionClient. Then build all the project and run.
However this solution didnt work for me too.
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...