I am building an Ionic app, but once the page is getting bigger, the app presents an scroll, there is any way to remove the scroll and let the app more native like?
My code has only 2 slides with some products description and category.
"Ionic Lab" is a deprecated desktop application, sunsetted in 2016. the Ionic CLI command "ionic serve" lets you serve the app locally in a browser. So it appears you're previewing your application in a web browser. When doing this, it's not going to appear or behave exactly as it will on a real mobile device. If you run a build, open your app in Xcode and test in the iOS simulator, you'll most likely see that no scrollbar is visible.
Testing locally in a browser with ionic serve is very practical and useful but the preview should not be believed to be a 100% accurate native preview.
Related
I have a XF app already published on the play store and now I am targetting iOS. During developpent I made sure the app was still working on iOS, using the simulator only.
On the simulator everything works as expected, the launch screen is shown then the MainPage starts. But when I debug on an actual IPhone device, the app get stuck on the Launchscreen.storyboard for about 20 sec then the app exits. I've no debug output and it seems that the AppDelegate is never hit. Breakpoints in AppDelegate.FinishedLaunching method are not hit for instance. I tried to F11 for start in debugging mode but I don't hit anything, still hanging on the launch screen. I was expecting the transition from simulator to device to be less painful.
My plist file contains the following permission requirements
...
<key>NSLocationAlwaysUsageDescription</key>
<string>We need to use your location</string>
<key>NSLocationWhenInUseUsageDescription</key>
<string>We are using your location</string>
<key>NSPhotoLibraryUsageDescription</key>
<string>This app needs access to photos.</string>
<key>NSPhotoLibraryAddUsageDescription</key>
<string>This app needs access to the photo gallery.</string>
The only difference I saw is that location permissions are not asked on the device while in the simulator it asks for it at start. But this might be related to the fact that I can't reach AppDelegate, I am not sure yet.
The iOS project was generated via Prism templates. I am using VS 16.8.0 on Windows, XF 4.8.0.1687, Prism 8.0.0.1909, Xamarin iOS SDK 14.4.1.3 and I am set to "don't link" for linkers option. The device is an Iphone 10.
Any idea how can I find out the root cause - or get some useful logs?
Thanks in advance for your help.
EDIT:
Here are the device log output during a new installation https://taits.s3-eu-west-1.amazonaws.com/devicelogs.txt. I am trying to go through them but kinda lost.
I'm reporting a very strange problem.
I have an app developed in Flutter and I have correctly integrated the Firebase library for using the Dynamic Links service.
The problem is when short links are open on a mobile device, it shows a screen with the message "Save my place in the app. A link will be copied to continue to this page", and a button OPEN to continue.
Using your link debugging tool everything seems ok
When I develop directly in debugging mode the problem does not present itself.
When I install the app from TestFlight sometimes it works and sometimes it doesn't. It seems random.
the problem could be that the app is not yet available on the store ?
Has anyone successfully installed the push notification system Goroost (https://goroost.com/) with Meteor JS?
The Goroost files are in my public folder, and I am able to hit the essential files of /roost.html, /roost_worker.js, and /roost_manifest.json
I am hosting my site on meteor.com, which may be a factor. The link to my site is here: http://oc_connect.meteor.com/.
I can get the subscription notification and push notifications working in a Safari desktop browser, but not Safari mobile and not Chrome either desktop or mobile.
Any advice gratefully received.
I've made it work by installing Force SSL https://atmospherejs.com/meteor/force-ssl which has kick started Android notifications.
And GoRoost does not currently work with Safari mobile, just Safari desktop. So, the problem is solved.
Having a problem debugging Android and IOS using Ripple. I am using the Blank App(Apache Cordova) project with no changes.
Problem:
The first time I build the project and test with Ripple, Chrome and Ripple work correctly. Subsequent builds causes JavaScript breaks that block the app from running. When I F5 thru the breaks, the Ripple UI and App appear in Chrome.
Steps To Repeat:
Open my blank Cordova app.
Select Debug > Android > Ripple - Nexus 7.
Build the app by clicking on the green build button. App runs fine.
Close the browser and stop debugging
Build the app again by clicking on the green build button. App does not appear in Chrome.
JavaScript highlighted in yellow appears in the IDE.
Click F5 to continue through breaks. Ripple and App appears in Chrome when all breaks have been viewed.
Fix:
None.
I can Continue (F5) the scripts until the app and Ripple appears in Chrome. Closing the project and reopening it will allow the app to run properly, but the problems repeat when I debug the project after the 1st attempt.
This is a bug that will be fixed in the next update. See this post for a full explanation and suggested workaround.
Ive been trying to add a button to properly exit an Android app, built using Flex 4.6. I have used the command NativeApplication.nativeApplication.exit(); which seems to work on the emulator, and kills off the emulator.
When I run it on a device, it doesnt exit, it actually seems to go to start of the app (my login screen) which is kinda strange.
I hypothesise that something system-wide is holding the app in process or re-starting it. Anyone had any experience with this?
That code should work. I use it in my android flex app with no problem. The application quits correctly and I am dropped back at the home screen. What version of Android are you using? I was using 2.3 when I did this. If you have it running in debug mode, do you see any errors output to the console? Using the debugger will also allow you to see if it is not quitting properly or restarting on quit(you would see the splash screen again if this was the case)