iOS emulator works, but ionic view broken, and ionic run not on device

App framework and dependencies up to date. Server and emulator tests work without errors. Ionic view of app worked months ago, early in development. Current version build and upload run without error.

In ionic view, updated app and cleared data. App launches with blue header and footer bars and header icon appearing, but footer icons and areas remain blank. App id is d5e1e9cc.

ionic run ios --livereload --consolelogs --serverlogs --device does not find iPhone 5s that is usb-connected, rolling over to iPhone 6 simulator (which works). May be missing something obvious: haven’t used ionic run with device before. doesn’t even indicate the --device option.

Make it simpler and use only ionic run ios --device and you Safari remote debugging to see what is going on your phone.

Setup safari on both ends as in how to, and started inspector. The following attempts were run with usb-connected iPhone 5s:

ionic run ios --device build fails with Check dependencies Code Sign error: No code signing identities found: No valid signing identities (i.e. certificate and private key pair) were found.

ionic run ios --consolelogs --serverlogs --device build succeeds, deploys emulator with no console message in inspector, and emulator performs as app in ionic view does (starts running, but fails to display ion-view content or footer tab icons).

ionic run ios --livereload --consolelogs --serverlogs --device deploys emulator and works fine that way.

Have you signed up for an Apple Developer account?
If you did, did you set up XCode with your certificates?

No. I was hoping ionic view would delay the day I needed the Dev account. Is that the only reasonable way forward? If so, that limitation needs to be advertised.

If you want to test your app on a physical device outside of Ionic view, then yes you’ll need a dev account. It’s a restriction Apple has in place.

So the iOS --device option can’t be expected to work w/o dev act, even via usb-connection?

And there’s no reasonable way to debug an ionic view failure (when emulator works), w/o --device connection?

I’d appreciate confirmation of both these suppositions. If both are true, time to get out my credit card for dev act.