Foreground-Notification does not work after app start

if i call FileDownloader.getImpl().startForeground() for the first time after app start, i get sometimes this:

W/FileDownloader.DownloadServiceNotConnectedHelper: request set the download service as the 
foreground service([354],[Notification(pri=2 contentView=null vibrate=null sound=null 
defaults=0x4 flags=0x3 color=0x00000000 actions=1 vis=PRIVATE)]), but the download service 
isn't connected yet.

is it necessary to issue the start() command of e.g. a FileDownloadQueueSet before to make sure the service is started? currently i call first startForeground() as i want to display the notification already, where in the meanwhile i’m fetching the download urls and starting the actual download after i get the download-url response.

if i then issue a second download afterwards, the notification works properly.

[Jacksgong]

I have an idea to make you do that easier, like below two pattern:

/** If the FileDownloader service isn't start and connected yet, will
 * block the thread to start service the connected to it, after connected
 * unblock the thread, and invoke startForeground(Notification); If the
 * FileDownloader service has already started and connected, just invoke
 * startForeground(Notification).
 */
FileDownloader.insureServiceBind().startForeground(Notification):void

/** If the FileDownloader service isn't start and connected yet, will start
 * and connecte to it asynchronous and return false, after connected to the 
 * service, invoke startForeground(Notification); If the FileDownloader 
 * service has already started and connected, just invoke 
 * startForeground(Notification) and return true.
 */
FileDownloader.insureServiceBindAsync().startForeground(Notification):boolean

[Jacksgong]

Sorry, It does not make sense because startForeground need a customize notification…