Titleview not visible on IOS - Maui - ios

I'm using Maui to create a cross-platform app. To navigate through the app the appshell is used. On Android everything is working fine, but on IOS the custom titleview isn't displayed right. After startup only the bottom half of the view is visible, and after I switch to a different tab and back, the titleview is gone completely. I'm not sure what I'm doing wrong. Is there any way to fix this?
(Maybe related to https://github.com/dotnet/maui/pull/12834 but I'm not sure)
xaml:
<Shell.TitleView>
<Grid>
-- content --
</Grid>
</Shell.TitleView>

This issue can be reproduced for iOS. Several issues on Github has mentioned this question: Shell TitleView disappearing on tab change #9687 and Title view not displayed after navigating shell tabs #9269.
Also, several workaround has been found, such as wrapping the shell in a navigation page and using a custom render for AppShell on iOS.
Seems so many issues are related to the commit you mentioned in the question. You could wait for the new release, update Visual Studio and reopen these issues if it still not work.
Hope it works for you.

Related

How to debug Ionic iOS swipe gesture issues

I am dealing with a weird bug on Ionic's iOS native build where I sometimes cannot swipe back or switch tabs once I transition to a new page using router.navigateByURL(...), and trying to debug this issue has been troublesome since I can't "see" how the gestures are handled. Does anyone know where I should be looking in the code for handling transition gestures?
Here's a video demo of the problem: https://streamable.com/hk9c0
In the video, you can see me:
Swiping down to refresh using the ion-refresher element and you can see the page beneath (already entered a bug report for that part: https://github.com/ionic-team/ionic/issues/18284 )
Trying to tap the back arrow in the left corner
Attempting to swipe left to right to go back a page (hard to show that one)
Tapping the bottom tabs to transition to new tab, at one point, I tap on a tab that has an ion-fab element which appears in the bottom right because its z-index is higher than the "stuck" page.
Currently the best I've been able to do is by looking at the css classes that are added to the pages, but it's not much use....
Where app-release is the page you can see in the video and app-home is the page underneath the stack. It's my understanding that Ionic uses hammer.jsfor gestures, so I added it as a tag, please correct me if I am wrong. I cannot, for the life of me, recreate this bug consistently, but will often trigger 1 out of 50 tries.
I've been digging through the utils in Ionic Core to see where elements are being added and removed, with no luck.
I created a bug request for this here as well: https://github.com/ionic-team/ionic/issues/18305
Are you using #angular/animations to make the transitions between the pages? I had some issues like yours, as you can see in my question.
Router navigate on Ionic with animation blinking on ios using angular animations
If I am right about the use of #angualar/animations I suggest to use a custom animation of the Ionic itself, and not te angular's. You can see an working example here of its use here:
https://github.com/mhartington/ionic4-custom-animation
Since I have less tem 50 rep I cant comment so I had to post this anwser not knowing if it was really your case. Hope it helps.

Xamarin Forms NavigationPage small part of previous page visible when navigating on iOS

I'm facing a very awkward trouble with my XF NavigationPage on iOS, and can't find anything about it on google. When I navigate from one page to another using Navigation.PushAsync there is 1pt line of previous page on the left of the screen visible untill replace that loading page's content from codebehind, you can see it here: screenshot (I actually have an image im my XAML and it's replaced with content that is loaded from server). If I disable animations with false param on PushAsync this dosen't happen.
Is there any way to preserve animations and get rid of this? Any suggestions appreciated, thank's in advance.
Update to the Latest version of Xamarin Forms, as I remember facing this bug on some previous version of XF probably 3.5 something but when i updated to the latest it started working
Good luck
Revert in case of queries

React Navigation Stack Navigator default shadow styling

I'm using React Navigation to construct a tab bar based type of an app in ReactNative.
"react-native": "0.44.0",
"react-navigation": "^1.0.0-beta.9",
I've got the navigation part pinned down and working. But with regards to styling I'm seeing a shadow on the StackNavigator (navigation controller) inside tab bar. Refer image below.
I'm not used to seeing this kind of a shadow on native iOS apps (I'm an iOS mobile dev trying out RN)
upon further investigation I saw that there are 'shadow' properties specified in 'Card.js' in ReactNavigation. So I manage to fixed the issue by passing in some overriding cardStyle like so
cardStyle: { shadowColor: 'transparent' }
Given all the above, I have two questions
Question 1
Why is this the default behaviour/styling?
To debug the issue, I decided to do a quick view debugging in Xcode and found that 'shadow' does not show up in there.
Question 2
Why is this happening?. Since RN app is essentially a native app (native iOS in this instance), isn't view debugging a reliable way to debug these kind of view related issues?

How to smoothly translate view in iMessage extension in iOS 10?

I have issue when I try to push view controller in willTransitionToPresentationStyle:. The view was blinking for a split second before it fully expanded. It might be a small glitch or bug since iOS 10 and Xcode 8 are still in beta. But when I manually requested to change presentation style to MSMessagesAppPresentationStyleExpanded by calling requestPresentationStyle: after I push view controller, it went to expand mode more smoothly. Does anyone have similar issue?
I have had similar problems with transitions in iMessage apps. I think this should improve considerably when iOS 10 and Xcode 8 come out of beta, but for now we have to deal with Xcode's bugs.
There's a few things I've done to make this look better. Inside my extension I have a method that checks the presentation style every time the view changes. This method manages two different UIs - one for MSMessagesAppPresentationStyleExpanded and one for MSMessagesAppPresentationStyleCompact. This method hides and shows specific views accordingly. In my compact UI I have a button that allows the user to expand the interface by clicking it (this is basically the same as clicking the up arrow at the bottom right of the screen).
I've noticed that if you let the user expand the messages app after the view has been loaded for a while the transitions are much smoother and less buggy. Not sure why this is the case, but you should give it a try. Also, I've found segues to be extremely buggy, so that's why I went with keeping everything on one view controller.

iOS NativeControls - showToolBarTitle() is not working (PhoneGap)

I just saw a post on the phonegap google group about the issue
iOS NativeControls - showToolBarTitle() is not working.
and have spent my last two days with searching a solution for this issue.
More specifically - I want to add a native iOS toolbar to my phonegap app with the following features:
Title at the middle (I prefer an image, but a simple String in white color is also fine).
Back button (at the left side).
Action button (at the right side).
Background color - I want to control the backgroud color of the toolbar (I want it to be green!)
Can you please help me in anyway to complete this tasks?
Do you have some partial working code like NativeControls toolbar?
P.S - I already implemented a tabbar with the NativeControls plugin.
Tnx!
Lior.
Recently I have rewritten nativecontrols plugin for cordova 3.0. I see this question is a little outdated, but probably someone would want to use this plugin. actionsheet and toolbar is working now, tabbar and navbar is WIP.
https://github.com/apla/me.apla.cordova.nativecontrols
BTW, in original repository toolbar is never works.

Resources