Android Phone And Ipad Combo

0 views
Skip to first unread message

Sadie

unread,
Aug 5, 2024, 3:59:19 AM8/5/24
to therzanoty
Iset up a field maps project several years ago and it was working great until a month or so ago. The information is linked from our Portal to AGOL and then used in field maps to collect field data. The process worked fine until recently we had a complaint that when using Android devices the options would no longer show up in a certain field after the point or polygon was created. So when trying to edit an existing feature or copying attributes, the domain list is no longer generating. There are other domains/combo box fields in the form and they work fine, but suddenly this specific one stopped working. After lots of republishing and troubleshooting, it looks like it has something to do with the forms. When the field isn't added to a form and just collected in the raw it works fine. When added to a form, with formatting or no formatting, it no longer works properly. If I make the options radio buttons it also works, but I don't want to have 50 radio buttons instead of a dropdown.

To add more information on the steps I have tried. I have republished a number of ways. I have tried individually connecting the layers vs all of them in one bunch of five. I have tried editing in map viewer and that works fine. I have tried to make sure there were no errors in the symbology, pop-ups, and templates (in Pro). I have created a whole new web map. I have tried starting from scratch with forms and removing all formatting from the features in Map Viewer...IE no expressions, no forms, no additional pop-up settings. The pop-ups are basic and field based, just displaying the input in the field.




Good afternoon. I'm sorry you are running into this issue with ArcGIS Field Maps. I have a few questions for you that could help us with troubleshooting your issue.

What version of Field Maps are you using and what is the make/model of your Android devices?

Also, can you confirm this is only happening with existing feature and not when you are creating a new feature or is it both?

You stated this is the only field this is happening with; do you have any other fields with 50+ items in the domain?

When your republished, did you delete the existing data then publish or did you republish over the existing data?

And lastly, have you updated or made any changes to the devices recently?


It is an invasive species project and we collect both points and polygons. Both fields have different domains with a large number of options in each, but they do differ some. Neither of them populate after the initial creation of the feature and act similarly in when the work and don't work.


I have tried republishing over the existing feature layer and a totally new one, but neither work as soon as the fields are added into a form. If the fields aren't added to a form, the field populates just fine. Also if the option to use a radio buttons instead of a combo box is used. It works just fine. But that isn't practical for the number of options we have. I looked through the values that have been entered and cleaned up any that didn't match the domain, but that didn't make any difference.


I did not make or change anything on my device. It probably is a newer version of Android than previously used, but I can't make the distinction of it working and not working before and after that. This has occurred from other android users on the project as well and I don't have specifics on their devices, but they are using the newest Field Maps version that I indicated.


I FINALLY fixed it after months of trying. I copied the domains the fields were using and pasted them back into the geodatabase as a copy and then changed the domain to the new copy and republished. It seems to be functioning correctly so far.


I've been a Mac user since early 2008, months before the first Android device was announced and three years before I bought my first Android phone. I felt like an outlier for a while, until I started meeting more like-minded people: Mac users who couldn't fathom the idea of iOS on their phone and chose Android instead. Just here on Android Police, six other colleagues straddle the ecosystem barrier and strive for a cross-platform digital existence like me. But every year at WWDC, Apple takes it upon itself to lure us in, and it's getting harder and harder to resist the temptation.


The reasoning behind my deliberate Mac plus Android choice is that I find Android's philosophy resembles MacOS's more than iOS ever did or does. It's tough to explain to those who are completely entrenched in Apple's ecosystem or those who have gone for the Windows and Android combination, but the gist is that MacOS gives me lots of control while getting out of my way in the same way that Android does, which can't be said about Windows or iOS. It's a completely subjective impression, and you might disagree, but this is what guides my choice.


So as someone who's made this combo part of their daily routine, I've already decided to forego many of the built-in apps in my Mac. Facetime, iMessage, Safari, Apple Music, Maps, Photos, News, and Notes have been put aside in favor of cross-platform solutions like WhatsApp, Telegram, Chrome, Spotify, Inoreader, Todoist, Google Duo, Maps, Photos, and Keep. I'm happy with my decision, even though there's a little bit of envy each time Apple announces new integrations between its services that make me wish I could have the same experience with my own Franken-patchwork of choices.


But come WWDC every year, all of these steadfast convictions start cracking up a bit more, to the point where I'm asking myself whether this whole braving-the-digital-elements approach is worth it. Take yesterday, for example. Apple rolled out the red carpet and brought out its ecosystem bling and blitz to show me a whole world of possibilities that only an iPhone would unlock on my Mac.


Then there's the new Airplay to Mac that would instantly mirror my phone to the Mac. I could get a third-party app to do that for my Pixel, but a native cast-like experience would definitely be faster, more seamless, and less buggy. Monterey also brought Shortcuts to the Mac, but what wasn't mentioned during the keynote is that these would be synced with iOS, so I could build and use the same automations on my phone and computer. And if you know me, you know I adore shortcuts and automations.


Add the synced tab groups in Safari across devices, the better integration of Facetime and iMessage with multiple other services on phones and computers, and the allure of the single ecosystem life becomes a bit more irresistible. Wouldn't it be simpler to make the jump to iOS and forget about Android and its better Gboard, default apps for everything, and consistent back gesture and text selection? Or wouldn't it be cheaper to ditch the Mac and go for a Windows or ChromeOS computer, but live without Finder, Spotlight, or all the little UX touches that make the Mac a joy to use?


Those are questions every rebel who ascribes to the Mac + Android philosophy has to ask themselves every year, and the clear-cut answer is becoming less clear and less cut each time. The cost of standing with each foot firmly planted on one side of the ecosystem divide is rising, and we're missing on so much more integration and simplicity by fighting the normal order of things.


For now, I've weighed the pros and cons and I think there's still more value for me in staying with my unorthodox combination, but there might come a day where the balance will tip to the other side, and that scares me. If Apple's Universal Control was a bit more magical and worked across iPhones too, I'd already be done for, but I'm safe for at least another year.


Start typing on your computer, then switch to your tablet, phone or computerAny USB-equipped or Bluetooth Smart ready device that supports an external keyboard (HID profile) with the touch of a button. Your mouse pairs with up to 3 devices for seamless multi-tasking.


A standard 19mm spacing between the keys provides a familiar desk typing experience. Together with a large strike area it prevents unintentional keystrokes. MK850 Performance features well-scooped keycaps to help guide the fingers to the center of the key for a clean stroke.


Type and switch seamlessly between your computer, tablet, and smartphone.Any USB-equipped or Bluetooth Smart ready device that supports an external keyboard (HID profile). Pair your mouse with up to 3 devices. MK850 Performance combo has been optimized for use with your operating systems including Windows, Mac, and Chrome.


On my last trip in 2022, I took my 13" MacBook Pro and regretted it, so I'm not planning on taking that again. I will have my iPhone (currently a 12 mini but planning to upgrade to a 14 before I leave) but was thinking about getting an iPad for my upcoming May trip to Scotland. I've had iPads before - both a regular one and a mini, but it's been a few years.


I have travelled with an ipad Mini and a regular sized one. The Mini is much lighter and will do everything that the regular size will do. My regular sized ipad in its case was just so heavy to lug around everywhere. Also upgrade to the 256 GB. 64 is just not enough nowadays.


Tammy, I would use it to access/modify my personal guidebook I'm currently building in Google Docs, sort through photos, upload them to my online journal, use it for mapping, sightseeing research and general web surfing. I know I can do all that with a phone but for me it's easier with something a bit bigger.


I travel with a iPad Pro and it is light weight and travels well in my backpack. I use mine for reading books (much better than reading on a iphone), internet surfing, I also find making reservations and getting advanced tickets easier with the iPad. It's like having my Apple mac with me but much lighter and easier to pack and travel with. I also load the Rick Steves guide books on my iPad and it works better than the phone, and I don't have to carry the book around with me. **Get at least a 256GB! ** The more memory the better, especially if your saving pictures and video to your iPad.

3a8082e126
Reply all
Reply to author
Forward
0 new messages