As i said in another question i "migrate" eclipse/maven code of android-annotation app 2.7.1 to gradle in 3.3.1 but when i open tab "devices" (the bottom middle) it crash but if i used store app its doesn't and i suppouse because some change from 2.7.1 to 3.3.1
I upload code
and crash in com.pandaos.smartconfig.DevicesFragment
#AfterViews
void afterViews() {
devices_list_listview.setAdapter(deviceListAdapter);
devices_recent_listview.setAdapter(recentDeviceListAdapter);
}
finish.
Some idea?
Thanks in advance.
As wondercsabo said, the original code wasn't copy correctly and there is no problem with version upgrade.
Thanks again wondercsabo
Related
I'm using AudioKit version 4.2 and I receive this error (see attached image) after installing my app on my phone (iPhone X) - Xcode error when using AKRhodesPiano
The error is thrown after the app is compiled and installed (after the app is being opened on the device).
This is the line that I'm using:
let pianoNote = AKRhodesPiano() // error
When I change this line to a different instrument, for example -
let pianoNote = AKPluckedString() // works good!
Can someone help me figure it out?
Some of the STK Physical models got screwed up on a recent release. We're hoping to have it resolved in AudioKit 4.2.1. Really sorry for the inconvenience.
The problem is solved on 4.2.2 and later.
Tested and verified.
https://cocoapods.org/pods/AudioKit
in one of my apps I need to read app version to validate it against some conditions. To read it I execute this code
var version: String {
return Bundle.main.object(forInfoDictionaryKey: versionKey) as! String
}
I added this functionality in version 2.2.0. It was working good in my debug builds, but when submitted to App Store it started to fail. To investigate it I added code that sends a non-fatal issue to Crashlytics with version in the message (added in 2.2.1).
And now there's a funny part - in Crashlytics logs I can see that some non-fatals are from version 2.2.1 with message "Version: 2.2.1", and some other ones are from version 2.0.0 with message "Version: 2.0.0". So app version 2.2.1 reads its version as 2.0.0.
Have any of you experienced such thing? Any ideas how to solve it?
I'm still a newbie in the mobile app development arena, please forgive me if I did not provide adequate information, probably because my lack of knowledge on its relevance. I'll edit with more info upon request.
Here's what I'm using to build my app on a Windows 7 64bit environment:
AngularJS 1.0
Phonegap Build 6.3.0 (cloud version)
cordova-android 5.2.1 (as shown on Phonegap build)
cordova-ios 4.2.0 (as shown on Phonegap build)
azure-activedirectory-library-for-cordova version 0.7.1
I'm testing on:
Android phone Samsung Galaxy SCH-I545 os version 5.0.1
iPhone 6S Plus os version 9.3.5
Everything went well with Android using ADAL plugin 0.7.1. However on iPhone, it kept going back to the login screen for authentication to our AD FS even though I already got authenticated the first time. I'm suspecting the token did not get stored in cache, that's why acquireTokenAsync kept getting called? I'm still trying to get my hands on a MAC to troubleshoot further.
Then, I updated to ADAL plugin 0.8.0 to see if that might solve my problem, but now Android stopped working and I got this error:
DEVELOPER_AUTHORITY_IS_NOT_VALID_INSTANCE
I debugged through using developer tool on both 0.7.1 and 0.8.0 and I saw no token coming back in acquireTokenAsync method in version 0.8.0. Switching back to 0.7.1 and Android works again.
Could anyone guide me on what might be causing this problem on my iPhone and Android? Maybe I'm missing additional settings or files? The way I updated the ADAL plugin was replacing the cordova-plugin-ms-adal folder under plugins and modify my config.xml file to spec="~0.8.0", that should be sufficient right?
* Update on cordova-android *
I finally got 0.8.0 working on my android device by turning off validateAuthority
var context = new Microsoft.ADAL.AuthenticationContext(authority,false);
I think it's because I'm using AD FS (found this comment in ADErrorCodes.h under adal-for-objc):
/*! The passed in authority URL does not pass validation, if you're trying to use ADFS directly you must disable authority validation. */
/*! An error was raised during the process of validating the authorization authority. */
AD_ERROR_DEVELOPER_AUTHORITY_VALIDATION = 101
* Update on cordova-ios *
Debugging in Safari developer tool, I don't have tokenCacheItems after the native method got called.
bridge.executeNativeMethod('tokenCacheReadItems',[this.authContext.authority, this.authContext.validateAuthority])
.then(function (tokenCacheItems) {
tokenCacheItems.forEach(function (item) {
result.push(new TokenCacheItem(item));
});
d.resolve(result);
}, function(err) {
d.reject(err);
});
I spent almost a week on this already and I really appreciate any help on this issue.
Good day! I have strange problem with Xcode 5.0.1. When I'm trying to run the app - it crashes with the following exception: UNCAUGHT EXCEPTION (NSInvalidArgumentException): must provide a file handle or pipe
I have also reinstalled Xcode (from the app store) and I have still obtained the same result.
I had this problem when updating from 5.0.0 to 5.0.1. The fix was that I was using 10.9 DP1. Now having 10.9, the final version and a fresh xcode install, it ran fine.
i have facing same problem but with little change resolve my issues.
Change littile syntex like as show below
-(void)SelectBg;
change to
-(void)SelectBg:(id)sender;
Thanks and happy coding
From my extensive reading, the iOS 5.1 localStorage/WebSQL behavior change that Apple instituted has been fully rolled into Cordova 1.6.0.
However, while running on my (new) application on Cordova 1.7.0 and iOS 5.1.1, I am still seeing ugly, incorrect behavior.
I use window.localStorage to store and retrieve data. E.g.
window.localStorage.getItem("activeFormId")
window.localStorage.setItem("activeFormId", formId);
These work flawlessly during the same session of the Cordova-based app. If I background the app with the main iOS button then resume, that usually works as well.
However, the moment I kill the application (double-tap, long-press, tap the red circle) and relaunch, all localStorage data is lost. I have verified this with jsconsole.com as well.
Are there additional steps I need to take to ensure the persistence bug fixes are working? Any help is greatly appreciated.
Try using 1.7 - I had a similar issue and once I upgraded to 1.7 everything worked like it used to.
Try using localStorage vs window.localStorage syntax.
Also set what ever you're trying to call as a global variable...
var globalVar;
function onDeviceReady(){
globalVar = localStorage.getItem('something');
}