I'm currently working on an add-in for OWA for desktop and mobile.
I have some issues when testing on my device and so I would like to use my desktop browser's Developer Tools to debug the JS and check the HTML / CSS.
Is there a solution to do so with my device or with an Android emulator ?
Thanks in advance
I haven't tried any of the Android browser emulators, but I've found the Emulation modes in Internet Explorer's dev tools to be very helpful. The various options for document mode, browser profile, user agent string, orientation and resolution should simulate most scenarios. Note that I believe that these are what are used by the testers at the Office Store who review add-ins submitted for publishing.
Otherwise I've relied on very liberal usage of logging to the console, but debugging JavaScript with the Outlook client from Visual Studio is the easiest by far.
This option may be helpful as well:
HOW TO: Debug Office Add-in In Office Clients without Visual Studio: https://www.itunity.com/article/debug-office-addin-office-clients-visual-studio-2783
Related
I have a Question regarding side loading apps created with React Native (Expo).
I have build my app and uploaded it on the Expo Servers. I managed to side load the App on an Android Device without any problems. Even Over the Air updates run perfectly!
Now my question is if someone has ever managed to side load an app on an IOS Device? Is this even possible?
Its pretty simple on Android but as I know IOS it wont be easy on there because they always make your life extra hard :D
If someone has a guide or some reference on how to side load an Expo app I would really appreciate it.
Edit: I checked out this link: https://docs.expo.io/distribution/building-standalone-apps/ - which says that it can be done with XCode somehow.
As I dont have a Mac and I never want to own a Mac is it possible to do this via a VM maybe?
Thanks ~Faded
It's not hard if you have Xcode. There's a few steps here, but it's not difficult.
Do an archive build in Xcode.
Right click the build in Xcode->Archive and select "Show in Finder"
Right click the .xcarchive in Finder frand "Show Package Contents"
Navigate to Product->Applications. There will be a .app file in there.
Connect your phone to your Mac if you haven't already
Open Xcode->Devices & Simulators
Select your phone
Drag the .app from the Finder onto the "INSTALLED APPS". This will install the app on the device
Sorry, just reread the OP. I guess if you can get the xcarchive or .app from Expo you should be able to side load it using the last few steps
There are few options to load app but they require either macOS system or paid Apple developer account.
You can build in xcode if you have access to native sources, so it wouldn't work with expo managed workflow, but it's possible if you eject. (macOS required)
You can create simulator build expo build:ios -t simulator (it will work only on simulator) (macOS required)
You can create adhoc provisioning profile and use it for build, it will be possible to install that app only on devices registered on your apple account. (requires paid Apple developer account)
You can side-load builds if you have enterprise Apple account
I have had a problem on Android Marshmallow (6.0) installing an apk from Google Chrome on the device. I have a Lollipop device (5~) that allows install, however the Marshmallow device just states "Cannot open file". I have no problem using Appgyver's supersonic package tool but with Ionic Package it won't allow me to install from an apk.
I've done some research and found that by using an alternative browser on the device such as firefox or by using a third party file manager I am able to install the apk. The article below suggests Google Chrome is now locking out app installs not on the play store but I'm doubtful of this theory due to being able to install other apk's ok.
Frostwire Article for workaround
This has been a common workaround used by other reports of a similar issue online and does work for my case. Unfortunately this is an effort required by the customer that is damaging to the ease of access to the application.
It seems to be an issue exclusive to Android 6.0 (not exclusively Ionic package built apk's). This being said as I am able to build an apk and install from Chrome using Appgyvers 'Supersonic' services using the same device so I'm lead to believe there is indeed a solution to the problem.
Be aware that I am using Ionic package to build a "release" version and customers cannot have "developer mode" turned on. As well as this I have "allow untrusted sources option" engaged.
Does anyone have any insight on this problem?
So I discovered the problem. It appears firefox and older versions of Chrome are far less picky with Content-Type headers on file downloads for apk's. The App was being downloaded with the content-type head of application/octet-stream. Firefox (Android 6) and Chrome (Android 5.1) took no notice of this when trying to figure out the file type and were happy enough installing.
However Chrome on Android 6.0 requires a content type of application/vnd.android.package-archive for it to discern the type of file it has downloaded.
Anyway I made that change on the download and it now works!
I followed this question's answer to get my debugger working but for some reasons I stuck at step 3:
Check the box at the top that says "Discover USB Devices". There should now be a list of virtual devices currently available to Chrome. Find the device you want to debug and click the inspect link.
My problem is there is no "inspect link". The app I want to debug is running and I enabled USB Debugging
There is no application to debug. You need to install
mobile Chrome Browser first.
How to install Google Play Services in a Genymotion VM.
Also you need at least Desktop Chrome 42 to make inspect accessible.
The question is simple: how to debug a website on Android stock browser? I know about the remote debugging feature, but it's only available through Chrome for Android (pretty useless for me - website is displayed improperly only on stock browser).
weinre is WEb INspector REmote. Pronounced like the word "winery". Or
maybe like the word "weiner". Who knows, really.
weinre is a debugger for web pages, like FireBug (for FireFox) and Web
Inspector (for WebKit-based browsers), except it's designed to work
remotely, and in particular, to allow you debug web pages on a mobile
device such as a phone.
http://people.apache.org/~pmuellr/weinre/docs/latest
From source:
Libraries not supported
versions of Prototype.js before version 1.7 are not supported, as they
do not support the JSON.stringify() API correctly. You will get an
alert() in the web page you are debugging if you attempt to debug it
with weinre and you are using an unsupported version of Prototype.js.
Platforms supported - debug server
Any platform that supports node.js.
Platforms supported - debug client
The browser where the debugger user interface runs.
Google Chrome Apple Safari Other recent-ish WebKit-based browsers
Platforms supported - debug target
The browser with the page you are debugging.
Android Browser application iOS Mobile Safari application
PhoneGap/Cordova other Platforms not supported - debug target
iOS 3.1.3 or earlier webOS 1.45 or earlier
I've successfully connected Firefox for Android to my desktop Firefox, I'm able to debug pages, and even install applications.
The problem is that installed applications do not start. And in result I can't debug them. Even worse, that now I'm unable to delete installed app from device, there is no such button, and my app is not listed among android apps like those which are installed from Firefox Marketplace.
Does anyone know how to deal with that, or it is now working yet?
Ubuntu 14.10 x64, Firefox 31.0, Firefox for Android 31.0 beta (used stable with the same result), Android 4.4.4 (CyanogenMod 11)
Unfortunetely you cannot debug installed Firefox OS apps on Android phone via Firefox for Android. You can only debug web pages in Firefox for Android via remote debugging. https://developer.mozilla.org/en-US/docs/Tools/Remote_Debugging/Firefox_for_Android In case of Firefox OS app, you have better use App manager or simulator. Of course, if you have Firefox OS phone, you can do this via remote debugging between Firefox OS phone and your desktop.
Here are the generic instructions (after which I'll address your specific issues):
Install mozilla-apk-cli using NPM:
npm install -g mozilla-apk-cli
Use it to generate a "debuggable" APK for your app from either a source directory or a URL to the mini-manifest:
mozilla-apk-cli /path/to/source/dir/ arbitrary-name.apk
mozilla-apk-cli http://example.com/path/to/mini/manifest.webapp arbitrary-name.apk
(Context-click > Inspect Element on the "Free" button in Marketplace to discover the mini-manifest URL for an app in the Marketplace.)
Install the APK on your Android device:
adb install -r arbitrary-name.apk
Launch the app on the device. Look to the notification area for a notification about which port the remote debugger server is listening on. Forward that port on your desktop, f.e. if the port is 12345:
adb forward tcp:12345 tcp:12345
Go to Web Developer > Connect… in Firefox on your desktop and connect to localhost at the forwarded port. Commence debugging!
Notes:
Use Nightly builds of Fennec for the best experience.
Bug 929382 tracks WebIDE (née App Manager) integration.
File bugs on problems you encounter!
Now, regarding your specific issues: It sounds like you've made it past app installation but are stuck on launching and running the app. How are you launching the app? For example, are you tapping the app's icon on Android's All Apps screen? And what do you mean when you say that apps "do not start"? Do you mean that nothing happens when you launch the app, or does something happen (f.e. a splash screen appears, perhaps followed by a white screen), but the app itself doesn't appear?
It would also be useful to know the manifest URL of the app you're testing, if it's a public hosted app; or get access to the source code, if it's a public packaged app!
Finally, note this related (identical?) question: How to install packaged app on Firefox for mobile?. I copied the generic part of this answer from it, but presumably they should be consolidated into a single answer (modulo the troubleshooting info, which is specific to the problem you're encountering).