Does aosp master branch contain future release features? - android-source

According to the aosp document the future release of Android is developed internally by google: https://source.android.com/setup/code-lines#about-private-code-lines. However if you download the master branch of aosp the code name is already P which is a future release:
repo init -u https://android.googlesource.com/platform/manifest
repo sync
cd [source root]
. ./build/envsetup.sh
lunch 6
PLATFORM_VERSION_CODENAME=P
PLATFORM_VERSION=P
TARGET_PRODUCT=aosp_x86_64
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_ARCH=x86_64
TARGET_ARCH_VARIANT=x86_64
TARGET_2ND_ARCH=x86
TARGET_2ND_ARCH_VARIANT=x86_64
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=darwin
HOST_OS_EXTRA=Darwin-17.3.0-x86_64-10.13.2
HOST_BUILD_TYPE=release
BUILD_ID=OC-DR1
OUT_DIR=out
The future release development is not visible to external google developers but what's the role of aosp master branch? How does it fit into the codeline graph shown here: https://source.android.com/setup/code-lines

Related

Why is this "illegal url" error appearing when running flutter doctor?

I have installed a new version of flutter in my macOS. But when trying to run
flutter doctor I get this
Downloading Dart SDK from Flutter engine <<<<<<< HEAD
05e680e202af9a92461070cb2d9982acad46c83c
=======
d3ea636dc5d16b56819f3266241e1f708979c233
>>>>>>> 18116933e77adc82f80866c928266a5b4f1ed645...
curl: (3) URL using bad/illegal format or missing URL
Failed to retrieve the Dart SDK from: https://storage.googleapis.com/flutter_infra_release/flutter/<<<<<<< HEAD
05e680e202af9a92461070cb2d9982acad46c83c
=======
d3ea636dc5d16b56819f3266241e1f708979c233
>>>>>>> 18116933e77adc82f80866c928266a5b4f1ed645/dart-sdk-darwin-x64.zip
If you're located in China, please see this page:
https://flutter.dev/community/china
Is there a known fix for this? I have looked for an answer, but they're mostly targeted towards Windows.
navigate to git folder
in git console: (be aware local changes are dismissed!)
git fetch --all
git reset --hard origin/master
This is what worked for me - deleted the flutter folder and replaced it with one from the official flutter webpage

"flutter channel stable" failed in docker image: cirrusci when publish pages to gitlab

I'm trying to publish my flutter page on gitlab which is the git host of my project. I'm using the ci configure like the following(from this post)
gitlab page CI configure
image: cirrusci/flutter:latest
before_script:
- flutter channel stable
- flutter upgrade
- flutter config --enable-web
- flutter pub get
pages:
stage: deploy
script:
- flutter build web
- cp -r build/web public
artifacts:
paths:
- public
only:
- live
The ci job failed in an error like:
...
$ flutter channel stable
Switching to flutter channel 'stable'...
git: fatal: 'origin/stable' is not a commit and a branch 'stable' cannot be created from it
Switching channels failed with error code 128.
...
What's the problem?
One thing worth to note is my flutter project locate in a subdirectory(ie., my-flutter-dir) of the repository root. Is it the reason? How to configure the CI script in this situation?
I've tried to add a cd my-flutter-dir as the first command in the before_script, but it still result in the same error.
It's turn out being an issue of the docker image. After I removed the flutter channel and flutter upgrade command in the befor_script part, everything is ok now.
Note if you have the flutter project in a subdirectory under the repository root, still you need to add cd you-flutter-dir command in the before_script. Also don't forget to put the .gitlab-ci.yml file in the root of the repository.

Vapor unable to deploy to Heroku: We don't have build instructions for 5.3

I was able to commit the changes to my Heroku repo but when I push it it shows the following errors:
remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Swift app detected
remote: -----> Using Swift 5.3 (from .swift-version file)
remote: -----> Using built-in clang (Swift 5.3)
remote: -----> Installing swiftenv
remote: -----> Installing Swift 5.3
remote: We don't have build instructions for 5.3.
remote: ! Push rejected, failed to compile Swift app.
remote:
remote: ! Push failed
I used the following commands:
$ git add .
$ git commit -am "make it better"
$ git push heroku master
I also changed the buildpack to vapor/vapor:
heroku buildpacks:set vapor/vapor
Why is this error happening, and how can I fix it?
I have even changed the swift version by following commands
echo "5.1.3" > .swift-version
git add .
git commit -m "Done"
and pushed it but it to Heroku shows the following error
package at '/tmp/build_8e6b47bc' is using Swift tools version 5.2.0 but the installed version is 5.1.0
Swift 5.3 doesn't appear to have been released yet, and the only Vapor buildpacks that I can find don't yet support it.
I think you're using this buildpack that uses Swift version 5.1.3 in its current documentation. Try reducing your Swift version to that (by editing your .swift-version file and committing) and redeploying.
Edit: Your new error indicates a Swift Tools version mismatch. I don't program in Swift, but it looks like this is defined by a line in your Package.swift file and that it is related to your Swift version:
The very first line of a package manifest indicates the Swift tools version required. This specifies the minimum version of Swift that the package supports. The Package description API may also change between Swift versions, so this line ensures Swift will know how to parse your manifest.
Try changing
// swift-tools-version:5.2
to
// swift-tools-version:5.1
then commit and redeploy.
I also recommend making sure that you are using the same version of Swift locally for development as you're targeting on the server.

Flutter doctor is not working

C:\Windows\system32>flutter doctor
Unhandled exception: ProcessException: %1 is not a valid Win32
application.
Command: C:\Program Files\Git\cmd\git.EXE rev-parse --abbrev-ref --symbolic #{u}
It seems like a potential issues involving tooling/Android SDK paths with spaces. Per this thread:
Moving some recent discussion over from
#9976 (older issue):
Potential issues involve tooling/Android SDK paths with spaces. We
currently run all CI with spaces in the SDK path. Since we build the
Gallery example (which is nested under the SDK), we're also covering
the case where the user Flutter project directory contains a space.
Other issues I can imagine that AFAIK we don't test for in our CI, but
probably should:
Space in Android SDK path (all OSes)
Space in Xcode path (on macOS)
Space in path of command-line tools such as ideviceinstaller, git, etc. (all OSes)
And looks like this issue was resolved by the Dart SDK fix that was landed in master channel.

Deploy Play app on Heroku from a subdirectory of git repo

I want to deploy a Play 2.0.4 app on Heroku using git push heroku master but I have moved the play root folder into a sub folder of my git repo. Is there a way to deploy from there?
Currently it misidentifies my project as a 1.2.4 Play app, then the compilation and the deployment fails.
-----> Play! app detected
-----> WARNING: Play! version not specified in dependencies.yml. Default version: 1.2.4 being used....
-----> Installing Play! 1.2.4.....
-----> done
-----> Installing ivysettings.xml..... done
-----> Building Play! application...
Install this git plugin.
https://github.com/apenwarr/git-subtree
Run "git subtree push --prefix **subfolder with app" heroku master"
You can add the version of Play you would like to a conf/dependencies.yml file your repo.
dependencies.yml:
# Application dependencies
require:
- play 2.0.4
It will then load the correct Play version.
I had the same issue, surprisingly no generic solution found. So I wrote a buildpack myself. Hope it is helpful
https://github.com/timanovsky/subdir-heroku-buildpack