I am using latest leanback version 27.0.0 in my app. Now am facing few key issues which was not there in the older version 24.2.1. The issue is like this.
I have registered the key events. So every time when I press "OK" buttons with the remote onKey() method will be called. but when I pause my app by pressing android home and resume it again onKey() method is not calling. But on resume, the key will be registered only.This issue was not there when I was using the older version of leanback.
Thanks in advance.
Related
We have a published app in the Teams App Store.
We have implemented BarCode scanner feature in the task module and it is working fine. However when code is scanned we want to close the task module right away by executing microsoftTeams.tasks.submitTask();
This method is working great on Android and it closes the task module window, but it does not work on IOS.
On IOS we are receiving this error:
This call is not allowed in the 'content' context.
We have also tried to add parameters result and appIds but it didn't help.
IOS app version:
Microsoft Teams
Version: 3.16.0
Build: 3.16.77.2021163502/1004 (general)
Calling Version: 2021.34.01.8
Release Branch: 2021Sep-T1
Any help would be appreciated.
I also ran into this issue. To fix it, I downgraded #microsoft/teams-js from 1.11 to 1.10 and the modal began working as expected in iOS.
ViewIsDisappearing gets called when we pull down the Notification Tray and ViewIsAppearing is called when we push the Notification Tray up.
This happens after upgrading our Xamarin Forms version to 4.8.0.1364 from 4.1.0
How do I prevent the calling of ViewIsDisappearing/ViewIsAppearing when the app is in Inactive state ? This was not there till 4.6
It has to be some other library triggering it, I just created a new project and tested but it the notification trail didn't trigger any of those events
In my cross-platform app I save application properties in the following way:
Application.Current.Properties["myValue"] = "Test";
await Application.Current.SavePropertiesAsync();
I then retrieve them later like this:
string myVal = Application.Current.Properties["myValue"];
This works perfectly when using the Android emulator. I can close the emulator down, and when I restart it again, my app data is preserved.
However, when I deploy this app to a physical Android device, data preservation works as expected until I close the app and open it again. At this point I retrieve an empty value. It's as though the data is only saved to memory (and not to file).
Furthermore, the iOS version of the exact same app works faultlessly. When I open the app up, all previous values have been saved and I can retrieve them.
What am I doing wrong on the Android version? Is there an Android setting, permission, or option which I need to enable to have the values saved between app sessions when actually deployed to a phone?
I had a similar problem where only the debug version saved Properties. I think we're still waiting for the bug fix, and this is the workaround on Xamarin Forms bugzilla.
In short: go to .Droid project settings -> Android Options -> Linker
and enter/add "System.Runtime.Serialization" to Skip linking assemblies.
Wow! After lots of research, I have getting solution for same issue in mine. Problem is that, when i store List or DataTable in Application.Current.Properties then all properties are removed after reopen app but if i store List or DataTable as serialize, it working fine.
In VS you need to enable the option:
Preserve application data/cache on device between deploys
You can find this at Tools > Options > Xamarin > Android Settings.
I don't know if this has stopped in the latest updates of Xamarin Forms, the data is available until the application is running similar to session but persistent storage does not work.
The best api I think available for this is Akavache https://github.com/akavache/Akavache.
You can read this blog https://codemilltech.com/akavache-is-aka-awesome/.
Update
There is a bug filed in bugzilla:
https://bugzilla.xamarin.com/show_bug.cgi?id=26444
I don't remember exactly which part of this solved the issue, but when I followed the instructions to prepare the Android application for release from start to finish, the issue went away. The problem occurred when debug builds were used on an Android device.
https://developer.xamarin.com/guides/android/deployment,_testing,_and_metrics/publishing_an_application/part_1_-_preparing_an_application_for_release/
The link details the suggested settings for the Android project when releasing to device. Following these instructions should solve the issue.
I just loaded Xcode 6 GM seed. Now I want to submit an update of my app.
Archiving works so far. But when I click "Submit", as soon as the upload loading bar appears Xcode crashes.
Do I need Yosemite?
I had to download the Application Loader from Apple because Xcode could not find it.
Do I need Yosemite?
No. Mine crashed the same way, so i uploaded my app using Xcode 5.1. It worked fine.
The Application Loader seems the only thing that works right now. Had the same problem, while uploading or even just validating.
Just export via Organizer and Upload via Application Loader helped.
I was faced same problem. Now it works fine.
Solution : Just accept new changed terms and condition from apple developer account and resubmit it.
Please Make sure you've accepted all of the new agreements & condition in the Member Center.
To check if you need to, you can go to the preferences -> accounts in XCode, and chose to view details of an account and attempt to refresh button. Here, XCode will warn you that you need to accept new agreements in the Member Center before you can refresh.
or just login to developer account and go to here https://developer.apple.com/membercenter/index.action
I was able to make Xcode work, but I had to go to iTunes connect and start the process there first by going "My Apps" and clicking on the plus sign. Fill in the info and hit save. Then try submitting with Xcode and it should work.
OK. Here's my $0.02.
1) Xcode 6GM crashes every single time for me. I am running 10.9.4. I have no idea how widespread the issue is, but it is 100% repeatable for me. I cannot use Xcode 6 to submit apps for review.
The crash happens during the upload. I have submitted a RADAR report and given crash logs.
2) I was able to submit using the App Loader. Here's how you do that:
2.1) In the Organizer, after you have done the Archive, select the latest archive for submit.
2.2) Instead of "Submit," select "Export."
2.3) Select the first choice (App Store).
2.4) Open the Application Loader.
2.5) Select "Choose."
2.6) Select the .ipa that you just saved in the export.
2.7) That will work. You may get a message teling you that the API file is too big for analysis. I got that for all 9 of the apps I just submitted. In my case, I ignored it.
I think they rewrote the whole application load from scratch, and that Xcode is still buggy as hell.
They had a deadline, and rushed it. It shows.
I expect both the server (Web) component and Xcode to apply patches soon.
In my case, I'm quite annoyed, as I had to rush out a fix for the arbitrary decision they made to change the way that the CLLocationManager works, which broke all my location lookups. The fix is simple, but there will be a period of time when I receive hate mail from the users that upgrade to iOS 8, and the app stops working.
Joy.
I just installed the official version from the App Store and now everything works fine.
I had the same problem. When XCode crashes during export or submit it means that you have non-valid certificate or provision profile in build settings.
Here is the solution:
Accept new changed terms and condition from apple developer account. (Just like Sandeep said)
Go to here to generate new provision profiles, for App Store & AdHoc (Tutorial)
Double click new provision profiles you downloaded to install them, and then XCode will never crash.
The problem is caused by XCode 6.0 does not handle provision profile migration properly. Developers should regenerate provision profiles for XCode 6+, but Xcode 6.0 fails to display this error message properly and crashes. (If you use XCode 6.1 Beta, it will display error messages for you, no crash. Then you will know that the problem is caused by "invalid"=="legacy" provision profile.)
After that, you can submit app and export Ad Hoc distribution for Testflight.
I got a problem with "deviceReady" event not fired in the combination of the following situation
1) IOS 7 (Android 4.4 tested ok)
2) Using Cordova 3.1.0 or 3.2.0
3) overwrite ( note not appending, basically changed the whole user agent string to some arbitrary string)the user agent natively following the instruction here Change Phonegap User Agent
(I can confirmed the user agent is modified by reading navigator.useragent)
4) Add org.apache.cordova.device plugin
If I removed Device plugin, but still loads other plugins like PushPlugin and globalization, "deviceReady" fired ok.
Try to step through the cordova IOS native code, but at this stage it does not reveal much.
Any help will be appreciate.
Thanks