WindowsStoreApp Failed certification,saying the App failed Touch Input - wpf

My WindowsStoreApp certification failed(not the first submission) in Windows Store recently. The Note from testers says
The app is not usable with touch input and no such limitation is
disclosed in the app description page. Please see:
http://msdn.microsoft.com/en-us/library/windows/apps/Hh761498.aspx
for some of the common interactions for keyboard, mouse and touch.
I dont have a Windows RT device to test, instead I test my App in a windows 8 PC. I used 'POINTER PRESSED' Event in my App for Navigations,calculations,etc. I had successfully uploaded this App to the store a lot of times,but this time it failed. I am confused. My App should support all sort of WindowsStore Devices.Please guide me.

Related

Open nuke software through chrome?

How to open a desktop application(like Nuke) through browser.
for example: RV software have a url protocol. we can use that (rvlink://).
I think this is what you're looking for:
https://support.shotgunsoftware.com/hc/en-us/articles/219031308-Launching-applications-using-custom-browser-protocols
Note that this is asking your operating system to "launch the thing registered with the requested custom browser protocol". Similarly you can have a hyperlink mailto:/// which opens the email application registered on the users computer. rvlink:/// is registered by RV as one of these custom browser protocols during it's installation.
If you want more control you would need a process running on the user's machine that you interact with. For example that's the approach shotgun's competitor ftrack took leveraging a local process they call ftrack connect (http://ftrack-connect.rtd.ftrack.com/en/0.1.17/developing/tutorial/custom_applications.html)
If you want to run something completely custom you could take a look at running your own RPC. You would initiate the registered RPC command from the web application. Check out http://www.zerorpc.io/ or https://crossbar.io/ for some more information.
Good luck!
I spotted in an earlier response of yours that you're using Shotgun and it's launch in RV features. In which case - are you aware of Shotgun Toolkit?
https://support.shotgunsoftware.com/hc/en-us/articles/219039788-Toolkit-Home-Page
It provides app launching via the website, which it accomplishes via Shotgun desktop (a desktop app). It used to work via a browser method that chrome etc moved away from so now requires the desktop app hook.
There's actually a huge amount that SGTK does, though I think you might be able to disable everything except the app launching if you wanted. We've got it implemented across 4 locations here and it's pretty decent.

Accessing Local Settings in Windows 10

I am developing a Line-of-Business app for a client. The client specified the devices that were supposed to be used (some Dell tablet with Windows 8.1). Now, that the development is almost done and we were ready to release the first phase of the application, the client informed us that they have changed their mind and all those Dell tablets will run windows 10. I upgraded one tablet that I used for development and testing to Windows 10 as well. The tablet uses a RESTful Web API to access data stored in a repository. Obviously, the URL of the Web API must be configured in the settings of the app before the app can retrieve any data from the repository.
So I create the App Package to sideload the app on the tablet. The installation works properly, the app starts well for the first time. I go into the settings, set the URL and close the app.
When I try to restart, the app gets stuck showing the Splash Screen. If I try to access the Settings, I am informed that the settings for my app are not available at that time. The only way to get out of this is to uninstall the app and reinstall it again.
This is the code I use to save and retrieve the settings:
public void SaveSetting<T>(string settingName, T value)
{
ApplicationData.Current.LocalSettings.Values[settingName] = value;
}
public T GetSetting<T>(string settingName)
{
var localSettings = ApplicationData.Current.LocalSettings.Values;
if (localSettings.ContainsKey(settingName))
{
var value = localSettings[settingName];
if (value is T)
{
return (T)value;
}
}
// else, in all other cases
return default(T);
}
An interesting thing I noticed is that sometimes, depending on what I try to save in the settings, the app starts. For example, I was playing with it and tried to save some garbage instead of the correct URL. So instead of "http://x.x.x.x:nnnnn" I saved "a". The app started correctly, I got past the splash screen but obviously, I couldn't get any data.
Any ideas as to what exactly is happening? Did the access method for local settings change in Windows 10?
I have been scratching my head over this for the past couple of days. Initially, I thought it is a matter of permissions to create the Local Settings file, so I dedicated a lot of energy trying to find a solution from that perspective. However, as I said, if I dump some garbage in the settings, it works, so it's not a matter of permissions. Could it be that and IP address like "x.x.x.x" needs to be saved in a different way than as a string?
Any advice would be highly appreciated.
TIA,
Eddie
After I added some logging to my application I was able to prove that the app had no issues reading the settings. It's what it tried to do with them that it did not work. The URL read from the settings was correct but when the app tried to make calls to the Web API, the calls threw an exception and the app stopped working. So this shouldn't have been a question in the first place.
Thanks, Eddie

Can't login into the CocoonJS Developer app

I want to log in into the CocoonJS Developer app (on iOS, iPad mini), but I got an error "CSRF protection". I aso tried "Connect with Google", but that isn't working either because of cookie settings or something.
What am I doing wrong?
Note: I also tried it on my iPhone 4S, but also without success.
I had the same thing, but now it just says unknown error. Maybe it doesnt like jailbroken iphones/ipads
another possibility (and the cause of my issue) is you're using the old cacoonjs app on your ipad mini. It's confusing because they left links to get that app on the appstore on their old website which is still online here: https://www.ludei.com/cocoonjs/
You have to now go to cacoon.io and follow instructions, the old services are no longer running. https://cocoon.io/

Trying to code sign Mac app with Developer ID - get com.apple.developer.maps entitlement is not allowed (error code -67050)

I am code signing a Mac app using my Developer ID certificate so we can send it to beta testers. Thanks to helpful articles here I made sure I have the right certificate and private key. (This is a new app id) When I select Developer ID and Archive, I select to distribute with Developer ID and it validates all the checks successfully (Using Xcode 6.1) and creates my app file. When I launch it I crash with this in console (another great tip found here to check console for the REAL error):
killed com.[appname.OSX][pid 5946] because its use of the com.apple.developer.maps entitlement is not allowed (error code -67050)
11/7/14 11:26:23.263 com.apple.xpc.launchd[1]: (com.VIPorbit.OSX.192016[5946]) Binary is improperly signed.
So, I know the docs say you cannot distribute an app with Maps outside of the MacApp Store, but I assume this mean selling Mac apps as is often done. We are using the Mac App Store all the way. Also I can successfully archive and submit to the Mac App Store and we're in review.
The challenge is we want to get this out to some beta folks and Maps is a key feature we've added. I really don't want to go the old route with getting this Mac info and adding it to the provisioning file, defeats the purpose of the Developer ID option.
Anyone else experience this?
You can't distribute an application utilizing MapKit with a Developer ID.
MapKit is an Mac App Store-only feature.
It's a shame that this is not clear from the documentation.
If you want to test the app before the Mac App Store submission, I am afraid you have to add beta-testers' machines to the provisioning profile and sign the bundle with a "Mac Developer: ..." code signing identity.
😔

I cannot compile "out-of-the-box" - google's example cloud backend IOS client

Why am I getting "duplicate symbol _kCloudBackendClientID" compiling the project "solutions-mobile-backend-starter-ios-client-master" from Google?
This is right out of the box - I have xCode 5.0.2 (5A3005)
I am trying out their Mobile Backend Starter... ugh so tedious to get this working.
As of March 28 2014.. yes, the google app engine mobile backend starter for ios is a real pain in the a** to get working. I'm using XCode 5.1 and managed to get it all working after about 8 hours of trial and error.
The setup guide is here -
https://developers.google.com/cloud/samples/mbs/ios/
There are a lot of steps required to get the push notification certificates and provisioning profiles and app id's setup properly. One stumbling block is that when doing development builds, XCode forces your bundle identifier to have ".dev" at the end. Be sure you have this in the provisioning profile that you create with the attached push notification certificate.
There are several things broken with the code. First the compiler error:
1) Change #include "Constants.m" to #include "Constants.h" in MessagesTableViewController.m
Now the runtime errors:
2) Add Splash1/2/3ViewController.h and .m to the project. If you don't do this you get a crash on startup related to some exception related to UIViewController
3) Implement this in CloudBackendIOSClientAppDelegate.m
- (void)application:(UIApplication *)application
didReceiveRemoteNotification:(NSDictionary *)userInfo
fetchCompletionHandler:(void (^)(UIBackgroundFetchResult result))handler
{
/* copy-paste the code from the previous didReceiveRemoteNotification */
//add this
if (handler)
handler(UIBackgroundFetchResultNoData);
}
This API seems to be new as of IOS7 and (I guess) is required to receive push notifications on IOS7.
The other thing I had to do was go into the app engine configuration on the app engine website. On the "Backends" tab, you have to make sure your 'worker' backend is started.
If you get all of this done properly you should be able to go down to the "Custom/Mobile Backend settings" tab, scroll to the bottom, and send a broadcast message successfully.
Hey Google people, if you are reading this you can compensate me with some free tech support on the next hurdles I have to jump through ;)

Resources