# Codename One Updates: FCM Default, Android API 28, HTTPS, and Component Inspector Enhancements

DevFeed: [Codename One Updates: FCM Default, Android API 28, HTTPS, and Component Inspector Enhancements](<https://devfeed.tech/articles/we-re-back-from-vacation-19209.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/back-vacation/>)

Author: Shai Almog

Published: 2019-09-02T00:00:00Z

Content type: release

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [Development](<https://devfeed.tech/topics/development.md>), [Android](<https://devfeed.tech/topics/android.md>), [migration](<https://devfeed.tech/topics/migration.md>), [HTTP](<https://devfeed.tech/topics/http.md>), [debugging](<https://devfeed.tech/topics/debugging.md>), [ui](<https://devfeed.tech/topics/ui.md>), [Google](<https://devfeed.tech/topics/google.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [development](<https://devfeed.tech/tags/development.md>), [google](<https://devfeed.tech/tags/google.md>), [http](<https://devfeed.tech/tags/http.md>), [migration](<https://devfeed.tech/tags/migration.md>), [ui](<https://devfeed.tech/tags/ui.md>)

## AI overview

This update describes Codename One changes after a break, including the switch from GCM to FCM as the default push-notification approach, migration of build servers to Android API level 28, HTTPS requirements for connections, and improvements to the component inspector.

## Source excerpt

Summer is finally over and the kids are going back to school/kindergarten so it's time to go back to our regularly scheduled posts. I won't be posting as often as before as I'll dedicate more time for support/development activities but still there's a lot to write about... During our time off we had a lot of changes, I'll repeat a few big ones which you might have run into already and cover a few that might have gone under the radar.